- On August 31, 2026, an attacker drained about $4.9 million from binary options markets on Injective, a blockchain built for onchain trading.
- Validators deployed an emergency upgrade, v1.20.3-safeharbor.1, that disabled binary options settlement on mainnet.
- Injective says its base chain, consensus, native INJ token and staked funds were not compromised. Outside researchers dispute parts of that account.
- No full postmortem has been published.
How the exploit worked
Metaverse Post reports that Injective builds each market ID by joining several fields without separators or length prefixes. That let an INJ-denominated insurance fund collide with the ID of a USDC binary options market. When a market settled, the system covered a USDC shortfall using the raw INJ balance and skipped the required haircut.
The attacker created 299 instant binary options markets over about 19 hours. Each used an oracle the attacker controlled and set to never report a price, which forced the no-price refund path. Trades matched across the attacker’s own accounts let them withdraw roughly twice their deposits per cycle. In one sequence cited by Metaverse Post, about 105,000 USDC produced withdrawals above 204,000 USDC. The funds went to Ethereum through Circle’s cross-chain transfer protocol and were swapped for ETH, about 1,980 ETH in total.
The response
CryptoSlate reports that block production stopped for about 3 hours and 42 minutes on August 31, starting near 16:10 UTC, while validators deployed the patch. It added a denomination check on insurance funds and turned off binary options settlement on mainnet. Some validators were jailed temporarily for missing the upgrade window, and Coinbase and Coins.ph restricted transfers for a time.
On September 1 Injective said the chain was “upgraded, not halted,” and that the attack touched a small number of ecosystem apps. The Crypto Times reports Injective as saying it was adding stronger invariant checks and real-time monitoring.
Who Benefits and How
For traders, the patch is protective but restrictive. Permissionless market creation lets anyone list a market, which is the feature the attacker used, and binary options settlement stays off on mainnet for now. Users should expect more changes as the project reviews its market ID design. This is not investment advice, and prices are not discussed here.
What is still disputed or unknown
- The $4.9 million figure is a researcher estimate of funds bridged to Ethereum. Injective has not confirmed a final amount or who absorbs any shortfall (CryptoSlate).
- Injective’s “upgrade, not halt” claim conflicts with on-chain data showing a gap of about 3 hours and 42 minutes between blocks.
- Researcher Earthling Paddy disputes that the flaw sat only in apps, because the attack used messages from native exchange and insurance modules.
- Metaverse Post said the attacker’s identity is unknown, and the loss figure and attacker details may change.
- The emergency patch shipped within about a day, but no independent audit shows the monitoring changes would catch the next attack.
Frequently asked questions
How much was taken?
About $4.9 million by researcher estimates. Injective has not confirmed a final figure.
Were other Injective markets affected?
Injective says the attack was limited to apps using binary options markets. A researcher disputes how far the flaw reached.
Did the chain stop?
Block data shows production paused for roughly 3 hours 42 minutes. Injective describes the event as an upgrade. The patch itself added an insurance fund denomination check and disabled binary options settlement on mainnet, per CryptoSlate.
Sources
- Metaverse Post: Injective exploited for $4.9M via market ID collision in binary options settlement logic (Sep 1, 2026)
- CryptoSlate: Injective disputes four-hour halt claim after $4.9 million exploit (Sep 2026)
- The Crypto Times: Injective confirms secure network upgrade after app exploit (Sep 1, 2026)
