Decentraland
Decentraland is a decentralized virtual social platform powered by the Ethereum blockchain. Within the Decentraland platform, users can create, experience, and monetize content and applications. Decentraland is built, governed, and owned by its users.
PoC required
KYC required
Select the category you'd like to explore
Assets in Scope
Impacts in Scope
Retrieve sensitive data/files from a running server such as /etc/shadow, database passwords, and blockchain keys (this does not include non-sensitive environment variables, open source code, or usernames)
Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as, changing registration information, commenting, voting, making trades, withdrawals, etc.
Performing malicious interactions with an already-connected wallet such as modifying transaction arguments or parameters, substituting contract addresses, submitting malicious transactions, stealing funds or assets.
Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield
Transaction & meta transactions replay attacks
Undesired destruction or burning of assets: wearables
Minting assets from unauthorized addresses
Improperly disclosing confidential user information such as email address, phone number, physical address, etc. bypassing system securities and it is not public.
Subdomain takeover of decentraland.org.
Retrieving sensitive user information, like user’s credentials.
Changing sensitive details of other users (including modifying browser localStorage) without already-connected wallet interaction and with up to one click of user interaction, such as email or password of the victim, etc.
Escape sandbox attack from scenes (injection of HTML or code injections in main thread from deployed scene code)
Out of scope
-
Best practice critiques
-
Frontrunning, including backrunning and sandwich attacks that may not lead to user funds or assets
-
Bugs in dependencies (unless they lead to equivalently direct attacks on Wormhole)
-
Any secret data checked into the repository. Such as API/AUTH tokens
-
Attacks requiring privileged access from within the organization
-
Crashes in play.decentraland.org or scene preview
-
Software defects in deployed scenes in play.decentraland.org
-
Issues related to scene code itself
-
Scenes deployed by users using malicious code that requires users to download or interact with it
-
Any vulnerability that requires the user to input commands in the browser console
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