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. 

Temporary freezing of funds

Network not being able to confirm new transactions (total network shutdown)

Direct loss of funds

Unintended chain split (network partition)

Modification of transaction fees outside of design parameters

Shutdown of greater than 10% or equal to but less than 30% of network processing nodes without brute force actions, but does not shut down the network

Shutdown of greater than or equal to 30% of network processing nodes without brute force actions, but does not shut down the network

Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original results

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Permanent freezing of funds

Protocol insolvency

Theft of unclaimed yield

Permanent freezing of unclaimed yield

Griefing (e.g. no profit motive for an attacker, but damage to the users or the protocol)

Smart contract unable to operate due to lack of token funds

Theft of gas

Unbounded gas consumption

Contract fails to deliver promised returns, but doesn't lose value

Execute arbitrary system commands

Retrieve sensitive data/files from a running server, such as:
- /etc/shadow
- database passwords
- blockchain keys (this does not include non-sensitive environment variables, open source code, or usernames)

Taking down the application/website

Taking and/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.

Subdomain takeover with already-connected wallet interaction

Direct theft of user funds

Malicious interactions with an already-connected wallet, such as:
- Modifying transaction arguments or parameters
- Substituting contract addresses
- Submitting malicious transactions

Injection of malicious HTML or XSS through metadata

Injecting/modifying the static content on the target application without JavaScript (persistent), such as:
- HTML injection without JavaScript
- Replacing existing text with arbitrary text
- Arbitrary file uploads, etc.

Changing sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as:
- Email
- Password of the victim etc.

Improperly disclosing confidential user information, such as:
- Email address
- Phone number
- Physical address, etc.

Subdomain takeover without already-connected wallet interaction

Changing non-sensitive details of other users (including modifying browser local storage) without already-connected wallet interaction and with up to one click of user interaction, such as:
- Changing the first/last name of user
- Enabling/disabling notifications

Injecting/modifying the static content on the target application without JavaScript (reflected), such as:
- Reflected HTML Injection
- Loading external site data

Redirecting users to malicious websites (open redirect)

Changing details of other users (including modifying browser local storage) without already-connected wallet interaction and with significant user interaction, such as:
- Iframing leading to modifying the backend/browser state (must demonstrate impact with PoC)

Taking over broken or expired outgoing links, such as:
- Social media handles, etc.

Temporarily disabling user to access target site, such as:
- Locking up the victim from login
- Cookie bombing, etc.

Unintended permanent chain split requiring hard fork (network partition requiring hard fork)

RPC API crash affecting programs with greater than or equal to 25% of the market capitalization on top of the respective layer

Permanent freezing of funds (fix requires hardfork)

Increasing network processing node resource consumption by at least 30% without brute force actions, compared to the preceding 24 hours

A bug in the respective layer 0/1/2 network code that results in unintended smart contract behavior with no concrete funds at direct risk

Codebase

Documentation

__Reward 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.

Title	Description	Link
Codebase	Injective Labs
Codebase	Injective Labs