Injective's mainnet stopped block production for approximately 3 hours and 42 minutes on August 31, and then resumed through an emergency patch; on-chain research indicates that attackers profited approximately 1,979.8 ETH, equivalent to about $4.88 million, by exploiting the binary options mechanism.

On-chain block height shows the network recovered from 181,027,006 to 181,027,007, with no block rollbacks during the downtime. QuickNode's status page recorded a complete halt in block production on the Injective mainnet that day; as of now, Injective has not released a complete post-incident report, and details regarding the conditions that triggered the pause, patch code, validator coordination process, and recovery decisions have not been disclosed by the project team.

Researchers pointed to the Frontrunner oracle, which has stopped maintenance but still retains registration status, as the attack vector. The data source of this oracle has been empty for a long time, and the attackers subsequently created 299 permissionless binary options markets referencing this oracle, causing the market to enter a no-quote refund mechanism when prices could not be obtained.

The core of the vulnerability is suspected to lie in the refund calculation: when the binary options market could not read prices, the system was supposed to return funds to participants, but after the related logic was exploited, the refund amount was approximately double the expected value. Attackers repeatedly created markets and triggered refunds, cumulatively extracting assets from the insurance fund or protocol liquidity pool; the issues of "insurance fund being exploited" and "actual losses at the protocol layer" still await verification from official ledgers and patch explanations.

The attackers then exchanged the USDC obtained for approximately 1,980 ETH and consolidated it into an Ethereum address that has not initiated any transfers. Public tracking indicates that this address has not moved funds, and the attackers are suspected of evaluating white-hat settlement options; this is a judgment by researchers and does not represent that the assets have been frozen, confirmed for return, or that the project team has reached a settlement.

Reports also state that the funding gap at the protocol layer may have been filled, but there have been no public governance votes, supplementary funding sources, changes in insurance fund balances, or independent audit confirmations. If the gap was filled by the core team, foundation, market makers, or other off-chain channels, the economic losses can be temporarily covered, but governance transparency, oracle management, and risk parameters for permissionless markets still need to be addressed separately.

Mechanically, the attackers connected the ineffective oracle to the refund logic by creating permissionless markets, amplifying limited losses that should have been borne by failed trades into extractable protocol expenditures; the chain halt cut off continued arbitrage and asset outflow but froze normal trading, liquidation, and fund transfers. Short-term funds typically sell INJ to price smart contracts, oracle, and governance uncertainties, with on-chain liquidity providers and derivatives users bearing the risk of the halt; if the funding gap is indeed filled, the patch closes the refund vulnerability and removes the ineffective oracle, the insurance fund and core ecosystem participants bear direct costs, while token holders mainly bear trust depreciation and subsequent governance risks.

Source: Public Information