CryptoSlate
Injective halted block production for nearly four hours on Aug. 31 to contain an exploit that bridged roughly $4.9 million to Ethereum, with the foundation releasing an emergency patch (v1.20.3-safeharbor.1) that disabled binary-options settlement on mainnet and added an insurance-fund denomination check. The foundation framed the pause as an "upgrade, not halted," but on-chain researcher Earthling Paddy pushed back on that characterization, noting the patch modified core protocol code used by the chain's native exchange and insurance modules rather than only application-level logic.
Why it matters
The episode reframes a routine operational decision as a structural transparency test. "Upgraded, not halted" reads clean in a foundation post, but the on-chain record shows block production simply stopped for four hours, one earlier block took about 37 minutes, validators were jailed for missing the upgrade window, and major venues including Coinbase and Coins.ph temporarily restricted INJ transfers. The foundation has not published a full postmortem, has not disclosed the ultimate loss allocation, and has not clarified whether the replenished ecosystem pool was restored by the foundation, developers, or another participant. The roughly $4.9 million sat unmoved in the attacker-linked wallet at the time of writing.
Market impact
INJ traded around $4.80, down roughly 3% over the prior 24 hours, with the response absorbing most of the narrative damage rather than the dollar figure. The bigger read is governance: emergency patches to core protocol code require a level of disclosure that "users weren't affected" cannot substitute for, and the foundation's framing will be the reference point the next time a major L1 needs to make the same call.
Frequently asked questions
-
What actually happened to Injective on Aug. 31?
Injective's block production stopped for nearly four hours on Aug. 31 while the foundation deployed an emergency patch (v1.20.3-safeharbor.1) to contain an exploit that bridged roughly $4.9 million to Ethereum. Validators were jailed for missing the upgrade window.
-
Was Injective really "upgraded, not halted"?
The foundation used that framing in its public statement, but the on-chain record shows block production simply stopped for four hours. On-chain researcher Earthling Paddy argued the patch modified core protocol modules, including the chain's native exchange and insurance code, rather than only application-level logic.
-
How much was drained in the Injective exploit?
Researchers estimate roughly $4.9 million was bridged to Ethereum during the incident, with that amount still sitting in the attacker-linked wallet at the time of writing. Injective has not disclosed the final loss allocation or which party absorbed any shortfall.
-
Why did Coinbase and Coins.ph restrict INJ transfers?
Both exchanges temporarily paused INJ transfers during the multi-hour block production pause to avoid settling on potentially inconsistent state while validators moved to the emergency release. Transfers resumed once the chain caught up.
-
Has Injective published a full postmortem?
No. As of writing, Injective has not released a full technical postmortem. Its statement said the attack vector had been contained and patched, and that the foundation was adding stronger invariants and real-time monitoring, but loss allocation and the replenishment of the affected ecosystem pool remain undisclosed.
CoinDesk
Lookonchain
TheBlock