Q2 2026 Security & Compliance Report67 incidents, $764M in losses, 88% from operational failures.
Get the report →

Audit name:

[SCA] s6k | ERC20 | Mar2023

Date:

Apr 4, 2023

Table of Content

→Introduction
→Audit Summary
→Document Information
→System Overview
→Executive Summary
→Risks
→Findings
→Appendix 1. Severity Definitions
→Appendix 2. Scope
→Disclaimer

Want a comprehensive audit report like this?

Introduction

We express our gratitude to the s6k Labs team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.

s6k is a company dedicated to providing high-quality software solutions at extremely cost-effective prices and the best possible results.

titlecontent
PlatformEVM
LanguageSolidity
TagsERC20
Timeline28/03/2023 - 05/04/2023
Methodologyhttps://hackenio.cc/sc_methodology→

    Review Scope

    Repositoryhttps://gitlab.com/s6k-labs/s6k-token-contract→
    Commit9f55463c99daa4b731dc15bb2362a4156a81f38a

    Audit Summary

    Total9.5/10
    Security Score

    10/10

    Test Coverage

    0%

    Code Quality Score

    8/10

    Documentation Quality Score

    9/10

    3Total Findings
    0Resolved
    0Accepted
    0Mitigated

    The system users should acknowledge all the risks summed up in the risks section of the report

    Document Information

    This report may contain confidential information about IT systems and the intellectual property of the Customer, as well as information about potential vulnerabilities and methods of their exploitation.

    The report can be disclosed publicly after prior consent by another Party. Any subsequent publication of this report shall be without mandatory consent.

    Document

    NameSmart Contract Code Review and Security Analysis Report for s6k Labs
    Audited ByHacken
    Websitehttps://www.s6klabs.com/→
    Changelog05/04/2023 - Initial Review
    • Document

      Name
      Smart Contract Code Review and Security Analysis Report for s6k Labs
      Audited By
      Hacken
      Changelog
      05/04/2023 - Initial Review

    System Overview

    The scope of the S6k Labs audit consists of an ERC20 token that is Burnable and Pausable. The Burning functionality can be done by token holders and addresses that are approved by the token holders. The admin and pauser roles are defined in the system, which can transfer locked ERC20 tokens in the contract and pause, unpause transfers of the token respectively.

    According to the documentation, the s6k Token will be used on a Launchpad platform for staking and receiving allocations on sales and as the main currency for s6k projects such as the marketplace.

    The files in the scope:

    • s6kToken.sol_: The Burnable and Pausable ERC20 token of the system.

    Privileged roles

    • DEFAULT_ADMIN_ROLE: Can transfer ERC20 tokens that are sent to the contract by mistake.

    • PAUSER_ROLE: Can pause, unpause transfer of tokens.

    Recommendations

    • Lock the pragma version for best practice.

    • Use the external declaration in functions that are not accessed from within the contract.

    Executive Summary

    Documentation quality

    The total Documentation quality score is 9 out of 10.

    • Functional requirements are provided.

    • Technical requirements are provided.

    • NatSpec is not provided.

    Code quality

    The total Code quality score is 8 out of 10.

    • The code follows Solidity Style Guides.

    • Unchecked transfer was used.

    • Floating pragma is used.

    Test coverage

    Code coverage of the project is 0% (branch coverage).

    • Tests are not provided but do not affect the score because the Lines of Code of the scope are less than 250.

    Security score

    Upon auditing, the code was found to contain 0 critical, 0 high, 0 medium, and 3 low severity issues. Out of these, 0 issues have been addressed and resolved, leading to a Security score of 10 out of 10.

    All identified issues are detailed in the “Findings” section of this report.

    Summary

    The comprehensive audit of the customer's smart contract yields an overall score of 9.5. This score reflects the combined evaluation of documentation, code quality, test coverage, and security aspects of the project.

    Risks

    The PAUSER_ROLE in the s6kToken contract has highly permissive role access and can pause the transfer of tokens without any restrictions.

    Findings

    F-2023-0868Functions That Can Be Declared External
    Status
    unfixed
    Severity

    Low
    F-2023-0867Floating Pragma
    Status
    unfixed
    Severity

    Low
    F-2023-0866Unchecked Return Value
    Status
    unfixed
    Severity

    Low
    Code
    ―
    Title
    Status
    Severity
    F-2023-0868Functions That Can Be Declared External
    unfixed

    Low
    F-2023-0867Floating Pragma
    unfixed

    Low
    F-2023-0866Unchecked Return Value
    unfixed

    Low
    1-3 of 3 findings

    Identify vulnerabilities in your smart contracts.

    Appendix 1. Severity Definitions

    When auditing smart contracts, Hacken is using a risk-based approach that considers Likelihood, Impact, Exploitability and Complexity metrics to evaluate findings and score severities.

    Reference on how risk scoring is done is available through the repository in our Github organization:

    Severity

    Description

    Critical
    Critical vulnerabilities are usually straightforward to exploit and can lead to the loss of user funds or contract state manipulation.

    High
    High vulnerabilities are usually harder to exploit, requiring specific conditions, or have a more limited scope, but can still lead to the loss of user funds or contract state manipulation.

    Medium
    Medium vulnerabilities are usually limited to state manipulations and, in most cases, cannot lead to asset loss. Contradictions and requirements violations. Major deviations from best practices are also in this category.

    Low
    Major deviations from best practices or major Gas inefficiency. These issues will not have a significant impact on code execution, do not affect security score but can affect code quality score.
    • Severity

      Critical

      Description

      Critical vulnerabilities are usually straightforward to exploit and can lead to the loss of user funds or contract state manipulation.

      Severity

      High

      Description

      High vulnerabilities are usually harder to exploit, requiring specific conditions, or have a more limited scope, but can still lead to the loss of user funds or contract state manipulation.

      Severity

      Medium

      Description

      Medium vulnerabilities are usually limited to state manipulations and, in most cases, cannot lead to asset loss. Contradictions and requirements violations. Major deviations from best practices are also in this category.

      Severity

      Low

      Description

      Major deviations from best practices or major Gas inefficiency. These issues will not have a significant impact on code execution, do not affect security score but can affect code quality score.

    Appendix 2. Scope

    The scope of the project includes the following smart contracts from the provided repository:

    Scope Details

    Repositoryhttps://gitlab.com/s6k-labs/s6k-token-contract→
    Commit9f55463c99daa4b731dc15bb2362a4156a81f38a
    WhitepaperNot provided
    RequirementsProvided
    Technical RequirementsProvided

    Contracts in Scope

    contracts
    s6k_token.sol - contracts › s6k_token.sol

    Disclaimer