PoC Required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Severity
Critical
Title
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Severity
Critical
Title
Direct theft of any user NFTs, whether at-rest or in-motion, other than unclaimed royalties
Severity
Critical
Title
Permanent freezing of funds
Severity
Critical
Title
Permanent freezing of NFTs
Severity
Critical
Title
Unauthorized minting of NFTs
Severity
Critical
Title
Predictable or manipulable RNG that results in abuse of the principal or NFT
Severity
Critical
Title
Unintended alteration of what the NFT represents (e.g. token URI, payload, artistic content)
Severity
Critical
Title
Protocol insolvency
Severity
Critical
Title
Execute arbitrary system commands
Severity
Critical
Title
Retrieve sensitive data/files from a running server, such as:
- /etc/shadow
- database passwords
- blockchain keys (this does not include non-sensitive environment variables, open source code, or usernames)
Severity
Critical
Title
Taking down the application/website
Severity
Critical
Title
Taking down the NFT URI
Out of scope
Default Out of Scope and rules
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