Illuvium
Welcome to the world of Illuvium. A shattered land of beauty and wonder. Travel the vast and varied landscape hunting dangerous beasts, then capture them to battle in the Arenas or trade via the exchange.
PoC required
Rewards
Rewards by Threat Level
Mainnet assets:
Reward amount is 10% of the funds directly affected up to a maximum of:
$100,000Rewards are distributed according to the impact of the vulnerability based on the Immunefi Vulnerability Severity Classification System V2.2 This is a simplified 5-level scale, with separate scales for websites/apps and smart contracts, 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 to be eligible for a reward. Explanations and statements are not accepted as PoC and code is required.
We understand certain vulnerabilities may cross impact boundaries and it may be difficult to estimate the economic damage for some vulnerabilities. Illuvium will make every effort to reasonably estimate this using the criteria mentioned in impact categories (below).
Critical vulnerabilities for smart contracts are rewarded in accordance with the amount specified in the table, but are capped at 10% of economic damage, whichever is lower.
High vulnerabilities for smart contracts are rewarded in accordance with the amount specified in the table, but are capped at 5% economic damage, whichever is lower.
There are 4 main things you can provide which will help us to evaluate your submission quickly:
- Add a summary of the vulnerability,
- Add a step-by-step exploit process so we can reproduce the issue (for issues where a PoC is required),
- List any additional material / references (e.g. screenshots, logs etc.),
- Elaborate the perceived impact, should the vulnerability be exploited.
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 in Illuvium. Previous audits of Illuvium smart contracts can be found at:
- https://certificate.quantstamp.com/view/illuvium-part-4-staking-v-2 (StakingV2)
- https://github.com/peckshield/publications/blob/master/audit_reports/PeckShield-Audit-Report-Illuvium-v1.0.pdf (StakingV2)
Payouts are handled by the Illuvium team directly and are denominated in USD. However, payouts are done in USDC.
Program Overview
Welcome to the world of Illuvium. A shattered land of beauty and wonder. Travel the vast and varied landscape hunting dangerous beasts, then capture them to battle in the Arenas or trade via the exchange.
For more information about Illuvium, please visit https://www.illuvium.io/.
This bug bounty program is focused on their smart contracts, website and app and is focused on preventing:
- Loss of funds (including yield, including freezing, theft),
- Frozen/malfunctioning contract state,
- Unavailability of web and/or blockchain assets,
- Authentication and authorization issues that could result in loss of user funds,
- Reputational damage
KYC not required
No KYC information is required for payout processing.
Proof of Concept
Proof of concept is always required for all severities.
Prohibited Activities
- 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
Feasibility Limitations
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.