However, only those in the Assets in Scope table are considered as in-scope of the bug bounty program.

If an impact can be caused to any other asset managed by Decentraland that isn’t on this table but for which the impact is in the Impacts in Scope section below, you are encouraged to submit it for the consideration by the project.

Bug reports from compensated team members of any Decentraland core units will not be eligible for a reward.

All team members of the audit companies Decentraland works with, and its third-party suppliers, including Immunefi itself and its subsidiaries, are not eligible for a reward.

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

Employees and team members of Decentraland third-party suppliers "to core units" that operate in a technical capacity will also not be eligible for a reward if the bug is related to the work assigned or if the bug reporter is leveraging privileged information coming from the agreed services.

[Decentraland](https://c212.net/c/link/?t=0&l=en&o=3541085-1&h=4099657792&u=https%3A%2F%2Fdecentraland.org%2F&a=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.

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

Reentrancy or frontrunning attacks with no users assets loss involvement but lead to an undesired product behaviour by design

Changing non-sensitive details of other users (including modifying browser localStorage) with/without already-connected wallet interaction and with up to one click of user interaction, such as changing the first/last name of user, or disabling notification

Any impact involving a publicly released CVE

Temporarily disabling users to access the sites without the possibility of solving it by logging in again, such as locking up the victim from login, cookie bombing, etc.

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)

Temporary freezing of funds/assets for any amount of time

Controlled loss of user assets

Unbounded gas consumption that lead to make the core contract functionality unusable

Defacing the sites, totally or partially, resulting in unauthorized visual changes of the site which could impact multiple users.

Redirecting users to malicious websites without their consent (Open Redirect)

Catalyst Content: Impersonation of a user to alter their stored content.

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.

Decentraland Smart Contracts

Rewards are distributed according to the impact of the vulnerability based on the [Immunefi Vulnerability Severity Classification System V2.2](https://immunefi.com/immunefi-vulnerability-severity-classification-system-v2-2). This is a simplified 5-level scale, with separate scales for websites/apps, smart contracts, and blockchains/DLTs, focusing on the impact of the vulnerability reported.

All web/app bug reports must come with a PoC with an end-effect impacting an asset-in-scope in order to be considered for a reward.  All Smart Contract bug reports require a PoC and a suggestion for a fix to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required.

High smart contract vulnerabilities to be calculated as __0.1%__ of the economic damage and capped at USD 500,000, primarily taking into consideration funds at risk, but also PR and branding aspects, at the discretion of the team. However, there is a minimum reward of __USD 20,000__.

All other rewards for the bug bounty program are scaled based on an internally established team criteria, taking into account the exploitability of the bug, the impact it causes, and the likelihood of the vulnerability presenting itself, which is especially factored in with bug reports requiring multiple conditions to be met that are currently not in-place. However, there is a minimum reward of USD 1 000 for each severity level for smart contracts, rewards will be provided at the determined fair value by the team depending on these conditions, assuming that the bug report is in-scope of the bug bounty program.

Decentraland has combined Critical and High Smart Contract impacts together, please refer to the High Smart Contract rewards and impacts respectively. 

The following vulnerabilities are not eligible for a reward:

  - Estate: The [getFingerprint](https://github.com/decentraland/land/blob/master/contracts/estate/EstateRegistry.sol#L317) function can run out of gas for Estates bigger than 4000 LANDs.
  - Collections: Missing the ERC165 interface registration.
  - All vulnerabilities marked in [https://github.com/decentraland/smart-contract-audits](https://github.com/decentraland/smart-contract-audits) 

Decentraland requires KYC to be done for all bug bounty hunters submitting a report and wanting a reward. The information needed are Name, Mailing Address and any ID. The collection of this information will be done by the Decentraland team.

Payouts are handled by the __Decentraland__ team directly and are denominated in USD. However, payouts are done in __MANA and USDT__, with a minimum of 20% to be done in USDT.

Decentraland

Codebase