The Sandbox Smart Contracts: Program info

RANGE OF BOUNTIES

• Low — USD 1,000 paid in $SAND
• Medium — USD 2,000 paid in $SAND
• High — USD 2,000-20,000 paid in $SAND
• Critical — USD 20,000-200,000 paid in $SAND

IN SCOPE VULNERABILITIES

Critical

• Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
• Direct theft of any user NFTs, whether at-rest or in-motion, other than unclaimed royalties
• Permanent freezing of funds
• Permanent freezing of NFTs
• Miner-extractable value (MEV)
• Unauthorized minting of NFTs
• Predictable or manipulable RNG that results in abuse of the principal or NFT
• Unintended alteration of what the NFT represents (e.g. token URI, payload, artistic content)
• Protocol insolvency

High

• Theft of unclaimed yield
• Theft of unclaimed royalties
• Permanent freezing of unclaimed yield
• Permanent freezing of unclaimed royalties
• Temporary freezing of funds for any amount of time
• Temporary freezing NFTs

Medium

• Smart contract unable to operate due to lack of token funds
• Block stuffing for profit
• Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)
• Theft of gas
• Unbounded gas consumption

Low Smart contract fails to deliver promised returns, but doesn’t lose value

OUT OF SCOPE

Smart Contract specific

• Incorrect data supplied by third party oracles
  • Not to exclude oracle manipulation/flash loan attacks
• Impacts requiring basic economic and governance attacks (e.g. 51% attack)
• Lack of liquidity impacts
• Impacts from Sybil attacks
• Impacts involving centralization risks

All categories

• Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
• Impacts caused by attacks requiring access to leaked keys/credentials
• Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
• Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
• Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
• Best practice recommendations
• Feature requests
• Impacts on test files and configuration files unless stated otherwise in the bug bounty program
• Impacts requiring phishing or other social engineering attacks against project's employees and/or customers

All bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward. Explanations and statements are not accepted as PoC and code is required.

Rewards for critical smart contract vulnerabilities are further capped at 10% of economic damage, with the main consideration being the funds affected in addition to PR and brand considerations, at the discretion of the team. However, there is a minimum reward of USD 50 000 and a maximum reward of USD 200 000 for Critical smart contract bug reports. In cases of repeatable attacks, only the first attack is considered unless the smart contract cannot be upgraded or paused.

High severity smart contract vulnerabilities will be further capped at up to 100% of the funds affected. In the event of temporary freezing, the reward doubles for every additional 5 blocks that the funds could be temporarily frozen, rounded down to the nearest multiple of 5, up to the hard cap of 20 000 USD. This is implemented in order to account for the increased relative impact based on the duration of the freezing of funds.

All calculations of the amount of funds at risk are done based on the time the bug report is submitted.

The Sandbox requires all bug bounty hunters to complete the program’s KYC requirements if they are submitting a report and wanting a reward. The information needed is an ID photo along with a scan of a utility bill to show residency proof.

Bug reports from compensated team members of any The Sandbox core units will not be eligible for a reward. Employees and team members of third-party suppliers to core units that operate in a technical capacity and have assets covered in this bug bounty program will also not be eligible for a reward. All team members of the audit companies The Sandbox works with, and its third-party suppliers, are not eligible for a reward.

Bug reports from team members and third-party suppliers of businesses and organizations that are not a The Sandbox Core Unit but have assets considered as critical infrastructure covered under the bug bounty program are also not eligible for the bug bounty program.

Bug reports covering previously-discovered bugs are not eligible for the program. If a bug report covers a known issue, it may be rejected together with proof of the issue being known before escalation of the bug report.

The following issues are considered known and are not eligible for a reward:

• Contract: ERC20BasicApproveExtension (Ethereum & Polygon) Method: paidCall Description: The paidCall method when called on Sand contract can add an allowance for the caller to transfer Sand tokens owned by the contract itself. However, the contract will have a sand balance only if users send it to the contract address by mistake.
• Contract: all the implementation contracts Description: the implementation contracts’ lack of initialization will end up with anyone owning/managing/minting tokens.

All issues previously highlighted in the following audit reports are also considered out of scope: https://github.com/thesandboxgame/sandbox-smart-contracts/tree/master/packages/core/documentation/audits

For proxy contracts, only the current implementation and any further updates to the implementation contracts are considered in scope.

All smart contracts of The Sandbox can be found at https://github.com/thesandboxgame/sandbox-smart-contracts. However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

• Avoid using web application scanners for automatic vulnerability searching which generates massive traffic.
• Make every effort not to damage or restrict the availability of products, services, or infrastructure.
• Avoid compromising any personal data, interruption, or degradation of any service.
• Don’t access or modify other user data, localize all tests to your accounts.
• Perform testing only within the scope.
• Don’t exploit any DoS/DDoS vulnerabilities, social engineering attacks, or spam.
• Don’t spam forms or account creation flows using automated scanners.
• In case you find chain vulnerabilities we’ll pay only for vulnerability with the highest severity.
• Don’t break any law and stay in the defined scope.
• Any details of found vulnerabilities must not be communicated to anyone who is not a HackenProof Team or an authorized employee of this Company without appropriate permission.
• Please note: Sandbox company is entitled to make the payment in their native token. The Reward time will be confirmed by the Sandbox team upon report approval.
• The total triage period is 10 days: 3 business days allocated to HackenProof triage and up to 7 days for the Sandbox team triage.

• Do not discuss this program or any vulnerabilities (even resolved ones) outside of the program without express consent from the organization
• No vulnerability disclosure, including partial is allowed for the moment.
• Please do NOT publish/discuss bugs

We are happy to thank everyone who submits valid reports which help us improve the security. However, only those that meet the following eligibility requirements may receive a monetary reward:

• You must be the first reporter of a vulnerability.
• The vulnerability must be a qualifying vulnerability
• Any vulnerability found must be reported no later than 24 hours after discovery and exclusively through hackenproof.com
• You must send a clear textual description of the report along with steps to reproduce the issue, include attachments such as screenshots or proof of concept code as necessary.
• You must not be a former or current employee of us or one of its contractor.
• ONLY USE the EMAIL under which you registered your HackenProof account (in case of violation, no bounty can be awarded)
• Provide detailed but to-the point reproduction steps