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

LeechProtocol

Audit name:

[SCA] Leech Protocol | Farming | Feb2023

Date:

Feb 9, 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 LeechProtocol team for the collaborative engagement that enabled the execution of this Smart Contract Security Assessment.

Leech Protocol allows users to easily farm on multiple chains. They deposit their liquidity into Leech Protocol, which then performs operations that the user would normally do manually. Leech has incorporated protocols like Curve, PancakeSwap, Uniswap, etc. with specific liquidity pairs that are monitored.

titlecontent
PlatformBNB Chain, Avalanche, Optimism
LanguageSolidity
TagsFarm
Timeline22/12/2022 - 08/02/2023
Methodologyhttps://hackenio.cc/sc_methodology→

    Review Scope

    Repositoryhttps://github.com/Leech-Protocol/farm-contract/→
    Commit3cc1690e3c1b6b21b15c37faab95accc4e7b025f

    Audit Summary

    Total10/10
    Security Score

    10/10

    Test Coverage

    100%

    Code Quality Score

    10/10

    Documentation Quality Score

    10/10

    3Total Findings
    3Resolved
    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 LeechProtocol
    Audited ByHacken
    Changelog29/12/2022 – Initial Review
    25/01/2023 - Second Review
    08/02/2023 - Third Review

    • Document

      Name
      Smart Contract Code Review and Security Analysis Report for LeechProtocol
      Audited By
      Hacken
      Changelog
      29/12/2022 – Initial Review
      25/01/2023 - Second Review
      08/02/2023 - Third Review

    System Overview

    CSS_LeechProcol is a mixed-purpose system with the following contracts:

    • Context.sol - Provides information about the current execution context.

    • Farm.sol - Allows users to deposit and withdraw funds.

    • FarmCore.sol - Contains setter and getter functions for storage variables.

    • Ownable.sol - Restricts and controls access to specific functions.

    • IERC20.sol - An interface of ERC20 token.

    Privileged roles

    • The admin of the Farm can block and unblock user from interacting with smart contract.

    • The admin of the FarmCore can set service percent, disable and enable all functions of the smart contract, set MINTVL, CAPY, MINAPY, farm service, farm pool and farm pair.

    • The owner of the FarmCore can set withdraw address, start and end the moving from farm to farm, add and remove admins.

    Executive Summary

    Documentation quality

    The total Documentation quality score is 10 out of 10.

    Code quality

    The total Code quality score is 10 out of 10.

    Test coverage

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

    • Deployment and user interactions are covered with tests.

    Security score

    Upon auditing, the code was found to contain 0 critical, 2 high, 0 medium, and 1 low severity issues. Out of these, 3 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 10. This score reflects the combined evaluation of documentation, code quality, test coverage, and security aspects of the project.

    Scoring Methodologyarrow right

    Risks

    In case of an admin keys leak, an attacker can lock access to funds that belong to users.

    Findings

    F-2023-1281Checks-Effects-Interactions Pattern Violation
    Status
    fixed
    Severity

    High
    F-2023-1280Highly Permissive Role Access
    Status
    fixed
    Severity

    High
    F-2023-1282Floating Pragma
    Status
    fixed
    Severity

    Low
    Code
    ―
    Title
    Status
    Severity
    F-2023-1281Checks-Effects-Interactions Pattern Violation
    fixed

    High
    F-2023-1280Highly Permissive Role Access
    fixed

    High
    F-2023-1282Floating Pragma
    fixed

    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://github.com/Leech-Protocol/farm-contract/→
    Commit3cc1690e3c1b6b21b15c37faab95accc4e7b025f
    WhitepaperNot provided
    RequirementsNot provided
    Technical RequirementsProvided→

    Contracts in Scope

    contracts
    Farm.sol - contracts › Farm.sol
    IFarm.sol - contracts › IFarm.sol

    Disclaimer