Immutable
Bounty Range
$1,000 - $1,000,000
external program
Immutable
Immutable is a global leader in gaming on a mission to bring digital ownership to every player by making it safe and easy to build great web3 games through the power of immutable NFTs.
For more information about Immutable, please visit www.immutable.com.
Immutable provides rewards in USDC on Ethereum, denominated in USD.
Smart Contract
| Severity | Max | Min |
|---|---|---|
| Critical | $1,000,000 | $50,000 |
| High | $20,000 | $5,000 |
| Medium | $1,000 | Flat |
Primacy of Impact
Mainnet assets: Reward amount is 10% of the funds directly affected up to a maximum of $1,000,000.
Minimum reward to discourage security researchers from withholding a bug report: $50,000
Reward Calculation for Critical Level Reports
For critical smart contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD 1,000,000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted. However, a minimum reward of USD 50,000 is to be rewarded in order to incentivize security researchers against withholding a critical bug report.
Repeatable Attack Limitations
If the smart contract where the vulnerability exists can be upgraded or paused, only the initial attack will be considered for a reward. This is because the project can mitigate the risk of further exploitation by upgrading or pausing the component where the vulnerability exists. The reward amount will depend on the severity of the impact and the funds at risk.
For critical repeatable attacks on smart contracts that cannot be upgraded or paused, the project will consider the cumulative impact of the repeatable attacks for a reward. This is because the project cannot prevent the attacker from repeatedly exploiting the vulnerability until all funds are drained and/or other irreversible damage is done. Therefore, this warrants a reward equivalent to 10% of funds at risk, capped at the maximum critical reward.
Reward Calculation for High Level Reports
High vulnerabilities concerning theft/permanent freezing of unclaimed yield/royalties are rewarded within a range of USD 5,000 to USD 20,000 depending on the funds at risk, capped at the maximum high reward.
In the event of temporary freezing, the reward doubles from the full frozen value for every additional 24h that the funds are temporarily frozen, up until a max cap of the high reward. This is because as the duration of the freezing lengthens, the potential for greater damage and subsequent reputational harm intensifies. Thus, by increasing the reward proportionally with the frozen duration, the project ensures stronger incentives for bug disclosure of this nature.
Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.3.
Immutable is a global leader in gaming on a mission to bring digital ownership to every player by making it safe and easy to build great web3 games through the power of immutable NFTs.
Immutable provides rewards in USDC, denominated in USD. For more details about the payment process, please view the Rewards by Threat Level section further below.
Immutable adheres to the Primacy of Impact for the following impacts:
Primacy of Impact means that the impact is prioritized rather than a specific asset. This encourages security researchers to report on all bugs with an in-scope impact, even if the affected assets are not in scope.
When submitting a report on Immunefi's dashboard, the security researcher should select the Primacy of Impact asset placeholder. If the team behind this project has multiple programs, those other programs are not covered under Primacy of Impact for this program. Instead, check if those other projects have a bug bounty program on Immunefi.
If the project has any testnet and/or mock files, those will not be covered under Primacy of Impact.
All other impacts are considered under the Primacy of Rules, which means that they are bound by the terms and conditions set within this program.
| Auditor | Link | Completed at |
|---|---|---|
| All Audits | https://github.com/immutable/contracts/tree/main/audits | 9 June 2025 |
The submission of KYC information is a requirement for payout processing.
Participants must adhere to the Eligibility Criteria. For all valid submissions, Immutable hired an external service to perform KYC verification which will request for hunter's government identification and other personal identifiable information.
Proof of concept is always required for all severities.
Category 3: Approval Required
Any testing on mainnet or public testnet deployed code; all testing should be done on local-forks of either public testnet or mainnet
Any testing with pricing oracles or third-party smart contracts
Attempting phishing or other social engineering attacks against our employees and/or customers
Any testing with third-party systems and applications (e.g. browser extensions) as well as websites (e.g. SSO providers, advertising networks)
Any denial of service attacks that are executed against project assets
Automated testing of services that generates significant amounts of traffic
Public disclosure of an unpatched vulnerability in an embargoed bounty
Any other actions prohibited by the Immunefi Rules
The project may be receiving reports that are valid (the bug and attack vector are real) and cite assets and impacts that are in scope, but there may be obstacles or barriers to executing the attack in the real world. In other words, there is a question about how feasible the attack really is. Conversely, there may also be mitigation measures that projects can take to prevent the impact of the bug, which are not feasible or would require unconventional action and hence, should not be used as reasons for downgrading a bug's severity.
Therefore, Immunefi has developed a set of feasibility limitation standards which by default states what security researchers, as well as projects, can or cannot cite when reviewing a bug report: