Cronos rewound ~11,000 blocks to reverse a $120.4M Tectonic exploit. The attacker pumped the TONIC token, then borrowed real assets against it. Validators clawed back $111.2M; $9.19M bridged
Cronos Network validators halted their blockchain on August 30 and rewound it by 10,961 blocks, discarding almost two hours of settled transactions to reverse a $120.4 million attack on Tectonic, the largest lending protocol in the ecosystem. The move restored around $111.2 million to affected balances. It also pushed Cronos into a decision most blockchains are designed to make impossible: rewriting confirmed history through validator consensus instead of letting the stolen funds stand. Crypto.com, whose brand sits directly behind the Cronos chain, kept its centralized app and exchange running on separate infrastructure throughout.
The attack ran on economics, not a broken line of code. The attacker seeded the scheme with roughly $5 million, then looped it through Tectonic 98 times, borrowing and redepositing the protocol’s own governance token, TONIC, against itself. TONIC trades against thin liquidity, so each cycle pushed its price higher with little resistance. Within about 20 minutes the token traded at up to 300 times its starting value.
Tectonic’s price feeds tracked that inflated number. That was the opening. With hyper-inflated TONIC counted as collateral, the attacker borrowed genuinely liquid assets such as stablecoins, bitcoin and ether across nine separate lending markets, then drained them in a single borrowing transaction worth $120.4 million. Anyone who followed the 2022 Mango Markets collapse on Solana will recognize the blueprint: manipulate a thinly traded asset upward, borrow real value against the fake collateral, and leave the protocol holding a worthless position.
Early headlines put the loss near $74 million. The protocol’s own post-mortem later set the borrowed figure at $120.4 million and the recovered amount at $111.2 million.
$120.4M Total fraudulent borrowing 100% of the total $111.2M Recovered through the rollback 92% restored $9.19M Bridged out before the halt 7.6%, unrecovered 10,961 Blocks erased about 1h 54m of history $122M→$3M Tectonic TVL after the attack lending market wiped outBy the time validators froze the chain at 14:32:47 UTC, most of the borrowed value had not moved. About 92% of it still sat on Cronos. That single fact drove the decision. Restoring the chain to block 90,896,188, the last block before the manipulation started, returned every affected balance to its prior state and reversed roughly $111.2 million.
The cost was finality. Rolling back to that block meant throwing away 1 hour and 54 minutes of confirmed transactions, 10,961 blocks in total, whether or not they touched the exploit. Traders who opened positions on unrelated Cronos apps during that window saw them repriced when trading resumed. The alternative was worse for users: restart the chain as it stood and leave the borrowed assets under the attacker’s control. Validators, coordinating overnight, needed several rounds to get every node running a patched build from the same state before block production resumed at 23:49:01 UTC.
12:38:56 Attacker deploys contracts and starts inflating TONIC against thin DEX liquidity 12:49:39 A single transaction borrows $120.4 million across nine markets against the inflated collateral 13:25:00 Team flags irregular on-chain activity and liquidity leaving the ecosystem 14:32:47 Validators halt the network at block 90,907,150 Overnight Validator consensus restores state to block 90,896,188 after several rounds of coordination 23:49:01 Block production resumes with balances back to their pre-exploit stateNot everything came back. The attacker moved $9.19 million off Cronos before the freeze, most of it bridged into Ethereum, and that money sits beyond the restoration’s reach. It represents about 7.6% of the stolen total. Cronos says it is working with bridge and exchange partners on reconciliation, but anything already sitting on another chain depends on those third parties, not on what Cronos validators can rewind.
Tectonic itself did not survive intact. Its total value locked fell from about $122 million to under $3 million, wiping out nearly the entire lending market on the chain even after balances were restored. Depositors got their tokens back. Confidence in the protocol did not return with them.
The reversal split opinion fast. Critics see a red line crossed. A blockchain that can rewrite confirmed history, they argue, offers no real finality, and Cronos caps its validator set at 100, which means a small group rewrote the ledger for everyone. To that camp the incident confirms a structural weakness rather than a rescue.
Supporters frame it as the responsible call. The intervention kept more than $111 million with ordinary users instead of a thief, and an ecosystem tied to a consumer brand like Crypto.com could not easily absorb a $120 million theft going through uncontested. The CRO token recovered more than 6% once the chain was stable again, which suggests the market read the rollback as damage control rather than a fatal flaw.
The immediate casualty is on-chain lending on Cronos, which now has almost no liquidity left to work with. Rebuilding Tectonic’s deposit base means convincing users that collateral pricing cannot be gamed the same way twice, and the protocol’s stated priorities point straight at that weakness: tighter risk controls on collateral and pricing, closer monitoring of unusual on-chain activity, and faster incident coordination across the ecosystem. Oracle design is the specific problem. Any lending market that prices a volatile, thinly traded governance token through feeds that can be pushed 300-fold in 20 minutes carries the same latent risk, on Cronos or anywhere else.
For users, Cronos says no action is required, since balances were restored on-chain, and it has warned that any recovery link or unsolicited direct message should be treated as a scam. Archive snapshots of the discarded chain history are posted at snapshot.cronos.com for anyone who wants to verify the restoration independently.
A week later the industry picked up a contrasting case to measure it against. On September 7, the Bitcoin settlement layer Liquid Network lost $320 million to a node-level software flaw, but the attacker there claimed to be a white hat and held the chain hostage, refusing to return the funds until developers shipped a patch. There was no rollback and no forced reversal, only a standoff over the price of a fix. Cronos rewrote its ledger to protect users and drew fire for it; Liquid left its ledger untouched and let an attacker set the terms. Both answers are now on the table for the next network that has to choose.
The post Cronos Erased 11,000 Blocks to Undo a $120M Exploit appeared first on ETHNews.
