Follow crypto hack news, exploits, bridge attacks, protocol breaches, and security lessons from major incidents across Web3.
The larger disclosure implies roughly 80,689 affected customers, though no combined total or row-level overlap check is public.
Bitquery traced 20.45 BTC through 34 Bitcoin swaps, and the main destination later held roughly 5 ETH less.
Ontology version 3.1.5 is mandatory for compatibility, while the attack path and wider service recovery remain undisclosed.
One transaction emptied 28.6% of supply from the bonded pool, while 1.66 billion attacker-held TAC remains unresolved.
The network stayed secure at the consensus level, but the emergency response jailed validators and disrupted exchange transfers.
Copied support records exposed varying combinations of identity, location and compliance data, while private keys and customer funds remained safe.
Cronos restored pre-exploit state, Ontology paused before a confirmed loss, and ICON halted after assets reached exchanges, exposing three different emergency powers and recovery risks.
New postmortems estimate about 700 agents joined the intrusion, while OpenAI’s largest planned frontier RL run remains on hold.
The Aug. 30 postmortem traces the replay flaw to mismatched serial-number checks and a 105-minute response gap.
