Q1 2025 Web3 Security ReportAccess control failures led to $1.63 billion in losses
Discover report insights
  • Hacken
  • Audits
  • yo-exchange
  • [SCA] YoEx / ERC20 / Jun2023
YO EXCHANGE logo

YO EXCHANGE

Audit name:

[SCA] YoEx / ERC20 / Jun2023

Date:

Jun 13, 2023

Table of Content

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

Want a comprehensive audit report like this?

Introduction

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

YO EXCHANGE is a cryptocurrency exchange platform that aims to provide a safe, user-friendly, and sustainable ecosystem for buying, selling, and trading cryptocurrencies.

titlecontent
PlatformBNB
LanguageSolidity
TagsERC20
Timeline03/06/2023 - 13/06/2023
Methodologyhttps://hackenio.cc/sc_methodology→

    Review Scope

    Repositoryhttps://github.com/yocryptoexchange/Contract.sol→
    Commitce7b641

    Audit Summary

    Total1.6/10
    Security Score

    0/10

    Test Coverage

    0%

    Code Quality Score

    6/10

    Documentation Quality Score

    4/10

    18Total 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 YO EXCHANGE
    Audited ByHacken
    Approved ByHacken
    Websitehttps://yoex.io→
    Changelog13/06/2023 – Initial Review

    • Document

      Name
      Smart Contract Code Review and Security Analysis Report for YO EXCHANGE
      Audited By
      Hacken
      Approved By
      Hacken
      Website
      https://yoex.io→
      Changelog
      13/06/2023 – Initial Review

    System Overview

    YO EXCHANGE is a cryptocurrency exchange platform that aims to provide a safe, user-friendly, and sustainable ecosystem for buying, selling, and trading cryptocurrencies. The platform offers enhanced security, low transaction fees, and a user-friendly interface for users to grow and build a sustainable future in the crypto space.

    PROJECTNAME_ is an ERC20 token composed by the following contracts:

    • Token  — simple ERC-20 token that mints all initial supply to a deployer. Additional minting is not allowed. It has the following attributes:

      • Name: Set by constructor

      • Symbol: Set by constructor

      • Decimals: 12

      • Total supply: Set by constructor

    Executive Summary

    Documentation quality

    The total Documentation quality score is 4 out of 10.

    • Functional requirements are provided but not implemented by the code.

    • Tokenomics is provided but not enforced.

    • Technical requirements are not provided.

    Code quality

    The total Code quality score is 6 out of 10.

    • The code duplicates commonly known contracts instead of reusing them.

    • The code presents unused functions and redundant contracts.

    • The development environment is not configured.

    • Outdated Solidity version.

    Test coverage

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

    • Tests not provided.

    Security score

    Upon auditing, the code was found to contain 0 critical, 6 high, 4 medium, and 7 low severity issues. Out of these, 0 issues have been addressed and resolved, leading to a security score of 0 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 1.6. This score reflects the combined evaluation of documentation, code quality, test coverage, and security aspects of the project.

    Findings

    Code
    ―
    Title
    Status
    Severity
    F-2023-1763Requirement Violation
    unfixed

    High
    F-2023-1762Requirement Violation
    unfixed

    High
    F-2023-1761Requirement Violation
    unfixed

    High
    F-2023-1760Requirement Violation
    unfixed

    High
    F-2023-1759Requirement Violation, Data Consistency
    unfixed

    High
    F-2023-1758Best Practice Violation
    unfixed

    High
    F-2023-1767Dusting, Data Consistency
    unfixed

    Medium
    F-2023-1766Unfinalized Code
    unfixed

    Medium
    F-2023-1765Copy Of Well Known Contract
    unfixed

    Medium
    F-2023-1764Outdated Solidity Version
    unfixed

    Medium
    1-10 of 18 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://github.com/yocryptoexchange/Contract.sol→
    Commitce7b641
    WhitepaperN/A
    RequirementsProvided→
    Technical RequirementsN/A

    Contracts in Scope

    YOEXCHANGE - YOEXCHANGE

    Disclaimer