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

Audit name:

[SCA] RedFox | NFT Auction | Sep2021

Date:

Sep 11, 2021

Table of Content

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

Want a comprehensive audit report like this?

Introduction

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

RFOX's vision is to be the global leader in immersive metaverse experiences focused on retail, media, gaming & rewards. RFOX token is the multichain digital asset that fuels the RFOX metaverse ecosystem and its immersive technology.

titlecontent
PlatformEVM
LanguageSolidity
TagsERC721, Auction
Timeline06/09/2021 - 09/09/2021
Methodologyhttps://hackenio.cc/sc_methodology→

    Review Scope

    Repositoryhttps://github.com/RFL-Valt/rfoxvalt-contract→
    Commit58aea1b30eaa81ce896994ad9b03c40027051d02

    Audit Summary

    2Total Findings
    2Resolved
    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 RedFox
    Audited ByHacken
    Websitehttps://www.rfox.com/→
    Changelog08/09/2021 - Initial Audit
    09/09/2021 - Second Review
    • Document

      Name
      Smart Contract Code Review and Security Analysis Report for RedFox
      Audited By
      Hacken
      Changelog
      08/09/2021 - Initial Audit
      09/09/2021 - Second Review

    Risks

    Smart contracts within the scope were manually reviewed and analyzed with static analysis tools.

    The audit report contains all found security vulnerabilities and other issues in the reviewed code.

    As a result of the audit, security engineers found 1 medium and 1 low severity issue.

    After the second review security engineers found all issues were addressed.

    Findings

    F-2022-1911The owner could withdraw an entire amount of BWP tokens
    Status
    fixed
    Severity

    Medium
    F-2022-1912Reading array length in the loop
    Status
    fixed
    Severity

    Low
    Code
    ―
    Title
    Status
    Severity
    F-2022-1911The owner could withdraw an entire amount of BWP tokens
    fixed

    Medium
    F-2022-1912Reading array length in the loop
    fixed

    Low
    1-2 of 2 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/RFL-Valt/rfoxvalt-contract→
    Commit58aea1b30eaa81ce896994ad9b03c40027051d02
    WhitepaperNot provided
    RequirementsProvided
    Technical RequirementsNot provided

    Contracts in Scope

    common\\meta-transactions\\ContentMixin.sol - common\\meta-transactions\\ContentMixin.sol
    common\\meta-transactions\\EIP712Base.sol - common\\meta-transactions\\EIP712Base.sol
    common\\meta-transactions\\Initializable.sol - common\\meta-transactions\\Initializable.sol
    common\\meta-transactions\\NativeMetaTransaction.sol - common\\meta-transactions\\NativeMetaTransaction.sol
    test\\MockBWP.sol - test\\MockBWP.sol
    utils\\OwnerPausable.sol - utils\\OwnerPausable.sol
    BWPAuction.sol - BWPAuction.sol
    BWPNFT.sol - BWPNFT.sol
    ERC721Tradable.sol - ERC721Tradable.sol

    Disclaimer