Injective is a lightning fast interoperable layer one optimized for building unmatched Web3 finance applications. Injective is incubated by Binance and is backed by prominent investors such as Jump Crypto, Pantera and Mark Cuban.
Triaged by Immunefi
PoC Required
KYC required
Rewards
Rewards by Threat Level
Reward amount is 10% of the funds directly affected, capped at the maximum critical reward of:
$500,000Mainnet assets:
Reward amount is 10% of the funds directly affected up to a maximum of:
$500,000Reward Calculation for Critical Level Reports
For critical Blockchain/DLT bugs, the reward amount is 10% of the funds directly affected, capped at the maximum critical reward [$500,000].
For critical smart contract bugs, the reward amount is 10% of the funds directly affected up to a maximum of USD $500,000. The calculation of the amount of funds at risk is based on the time and date the bug report is submitted.
For critical web/apps bug reports will be rewarded with [$50,000], only if the impact leads to:
- A loss of funds involving an attack that does not require any user action
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. The amount of funds at risk will be calculated with the impact of the first attack being at 100% and then a reduction of 25% from the amount of the first attack for every 1h the attack needs for subsequent attacks from the first attack, rounded down
Reward Calculation for High Level Reports
-
High impacts concerning theft/permanent freezing of unclaimed yield are rewarded within a range of [$25,000] to [$100,000] with the reward calculated based on 100% of the funds at risk, though capped at the maximum high reward.
- If the duration of temporary freezing is 1h or less, then the severity level will be reduced to Medium if the amount is equal to or greater than USD 25 000. If not, the severity level will be downgraded to Low.
- There needs to be a minimum of USD 10 000 at risk in order for a report to be considered High.
-
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.
Reward Payment Terms Payouts are handled by the Injective team directly and are denominated in USD. However, payments are done in Stablecoins.
The calculation of the net amount rewarded is based on the average price between CoinMarketCap.com and CoinGecko.com at the time the bug report was submitted. No adjustments are made based on liquidity availability.
Program Overview
Injective is a lightning fast interoperable layer one optimized for building unmatched Web3 finance applications. Injective is incubated by Binance and is backed by prominent investors such as Jump Crypto, Pantera and Mark Cuban.
For more information about Injective, please visit https://injective.com/
Injective provides rewards in stablecoins, denominated in USD. For more details about the payment process, please view the Rewards by Threat Level section further below.
Primacy of Impact vs Primacy of Rules
Injective adheres to the Primacy of Impact for the following impacts:
- Blockchain/DLT : Critical
- Smart Contract : Critical
- Web/App : Critical
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. For more information, please see Best Practices: Primacy of Impact
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.
Public Disclosure of Known Issues
Bug reports covering previously-discovered bugs (listed below) are not eligible for a reward within this program. This includes known issues that the project is aware of but has consciously decided not to “fix”, necessary code changes, or any implemented operational mitigating procedures that can lessen potential risk.
- Vulnerabilities found in vendor systems such as Cosmos-SDK, IBC, CometBFT and CosmWasm fall outside this policy and should be reported to the respective vendor following their disclosure policy (if any)
KYC required
The submission of KYC information is a requirement for payout processing.
Additional information: A contracted technical contributor who is being directly compensated by the project or directly compensated by a contracted organization providing technical services to the project. A former contracted technical contributor who, for the past year from the date of the bug report submission, was directly compensated by the project or was compensated by a contracted organization to the project. In the case of the latter, the status of the organization’s contract with the project is irrelevant.
Proof of Concept
Proof of concept is always required for all severities.
Responsible Publication
Category 3: Approval Required
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.