Cronos has recovered most assets linked to the Tectonic lending exploit through an emergency chain rollback. However, about $9.2 million remains unrecovered after the attacker moved the funds across blockchains before validators halted the network.
Tectonic said the attacker exploited the pricing of its TONIC token and borrowed $120.4 million in assets during a single transaction. The incident emptied nine lending markets and triggered an emergency response from Cronos validators.
The attacker escaped with a relatively small portion of the stolen assets before the network stopped producing blocks. Tectonic now puts the unrecovered amount at about $9.19 million.
Cronos Rolls Back the Exploit
Cronos halted its blockchain on Aug. 30 and later restored the network to a state before the attack. The rollback removed the exploit transactions from the active chain history.
Blockchain analysis found that the rollback erased roughly $111 million in attacker-controlled assets that remained on Cronos. The network discarded nearly two hours of transaction history as part of the emergency measure.
The rollback prevented the attacker from retaining most of the assets borrowed from Tectonic. However, it could not reverse transactions that had already crossed onto other blockchains.
Funds That Escaped the Network
About $8.3 million had reached Ethereum before Cronos halted block production, according to blockchain tracking. Tectonic’s latest accounting places the remaining unrecovered funds at roughly $9.2 million.
The incident highlights the risks of using thinly traded tokens as collateral in decentralized lending markets. The attacker was able to sharply increase TONIC’s apparent value and then use the inflated collateral to borrow more liquid assets.
Tectonic has indicated that it plans to remove low-liquidity tokens from its collateral framework. The protocol’s response could therefore lead to tighter risk controls across its lending markets.
Cronos has resumed normal block production, while investigations into the exploit and the remaining funds continue. The case also raises broader questions about blockchain rollback powers and how decentralized networks should respond when large DeFi attacks occur.
