Injective, a Binance-incubated Layer 1 blockchain focused on derivatives trading, stopped producing blocks for 3 hours and 42 minutes on August 31 after an exploit extracted $4.9 million from the network. The chain resumed without a rollback after an emergency patch, according to block timestamps and QuickNode network monitoring data.
The exploit targeted a flaw in binary options settlement logic involving a market-identifier collision, according to on-chain analysis. Injective's halt lasted from 16:10 to 19:52 UTC, a full network stall that forced validators offline before the network recovered. The stolen funds moved through smart contract interactions tied to the platform's derivatives infrastructure rather than compromising validator security or consensus mechanisms.
Injective is a specialized blockchain built for on-chain perpetual and derivatives trading, backed by Binance and operating independently since 2021. It handles spot and futures markets across crypto pairs, with daily volumes typically in the hundreds of millions of dollars. The platform's focus on low-latency order matching and settlement makes it a target for logic-layer attacks that exploit pricing or collateral calculation code rather than core network consensus.

Ontology, a separate Layer 1 focused on identity and data verification, also halted block production around the same time on August 31 as a precautionary measure. Ontology said on September 1 that it had identified malicious activity targeting the network but confirmed user assets were not compromised. The network did not disclose the exploit amount or technical mechanism behind the halt.
The two incidents occurred amid a broader August spike in crypto security breaches. Industry data tracked $136 million in losses across hacks in August alone, a 67 percent increase month-over-month according to reports from September 1. Both Injective and Ontology resumed normal operations without requiring user intervention or asset recovery procedures.
Injective's three-hour halt and emergency patch represent a rare network-wide consensus failure for a major Layer 1. Most derivative blockchains rely on active validator sets to catch and respond to contract-level exploits within consensus parameters; a full production halt came after validators acted in coordination to prevent further damage before patching and restart. Ontology's precautionary halt showed no exploit amount or confirmed user impact, a defensive posture rather than evidence of active fund loss.