If an impact can be caused to any other asset managed by Illuvium that isn’t on this table but for which the impact is in the Impacts in Scope section, you are encouraged to submit it for the consideration of the project. This applies to only Critical and High impacts.

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.

Substantial loss of funds (>=1,000,000 USD) resulting in direct benefit of a malicious party

Complete authentication bypass (ability to fully impersonate another user/player and perform financial actions on their behalf)  - except those excluded via the out-of-scope section below

3rd party API key/token leakage that could cause substantial financial loss

Private key / seed / mnemonic leakage that could cause substantial financial loss

Loss of funds that does not result into direct benefit of a malicious party or the benefit to the malicious party is relatively small compared to the financial impact (in terms of cost of effort to address, brand damage as well as damage to treasury funds)

Code/system command execution on a remote system which would undermine all server-side controls

Subdomain takeovers which could lead to financial loss (e.g. initiate / sign transaction from the taken-over domain)

Vertical privilege escalation (e.g. a player performing administrative or internal tasks which could circumvent business logic or server side controls)

Persistent XSS which could result to financial loss

Issues that do not directly result in loss of funds, but may have indirect financial impact (cause brand damage, or result in temporary unavailability of a service/contract, or lead to significant increased gas costs

DoS excluding load-based (D)DoS

NoSQL/SQL injection without financial loss

Improperly disclosing user information that could be used to identify a user in conjunction, e.g. email address and wallet address pair)

Open redirect

CSRF

Reflected XSS

SSRF

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 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](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](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__. 

Illuvium

Resources & Documentation