Key points

  • September 8 reporting puts funds transferred off Cronos at $9.19 million.
  • Roughly $111.2 million in affected value was reversed following the August 30 exploit.
  • The updated accounting does not establish that all funds have been recovered.

Cronos has put the amount transferred beyond its network during the Tectonic exploit at $9.19 million, according to reporting published on September 8. The new accounting separates those funds from the much larger volume of borrowing that validators were able to reverse by restoring an earlier blockchain state.

Cointelegraph reported that the incident involved approximately $120.4 million in affected borrowing and that the rollback reversed around $111.2 million. The amount transferred off-network represented about 7.6% of the total, rather than a complete recovery of the assets involved.

Earlier coverage: Liquid Network recovers 3,400 BTC as restart preparations continue

An update on an earlier attack

The underlying exploit occurred on August 30; today's development is the additional accounting, not another attack. The Block's September 8 coverage also reported roughly $9.2 million unrecovered and described validators restoring the network to its final block before the exploit.

That distinction matters when comparing incident headlines. The value moved through a lending protocol, the balances reversed on its host blockchain and the assets transferred elsewhere measure different stages of the same event; they should not be added together as separate losses.

Collateral pricing was central

Bitquery's original on-chain investigation, published August 31, traced the mechanism to inflated collateral values involving TONIC, Tectonic's governance token. It described repeated borrowing and redepositing, followed by market purchases that pushed the price used by the lending platform sharply higher.

The researchers counted nine lending markets and 11 transfers in the transaction that drained available liquidity. Their analysis included both stablecoins and other assets, explaining why a count focused on only part of the transfers could produce a smaller incident estimate.

A lending platform depends on collateral valuations to determine how much a borrower can withdraw. When that valuation rises without a comparable increase in realizable market value, the resulting borrowing capacity can diverge from the security actually available to repay lenders.

Reversing one chain has limits

Cointelegraph reported that the activity was detected at 12:49 UTC on August 30, with validators halting Cronos at 14:32:47 UTC. Block production resumed at 23:49:01 UTC after balances were restored, according to its account of the post-mortem.

The Block identified the halt point as block 90,907,150 and the restoration point as block 90,896,188. Those coordinates describe the network intervention; they do not establish that assets already transferred to another blockchain were returned.

Bitquery's earlier investigation traced about $8.3 million to Ethereum and documented transfers shortly before the halt. That was an earlier research estimate; it should not replace the $9.19 million figure in the latest reporting or be presented as a second, additional loss.

What remains to be established

The reviewed reports establish that the rollback reversed most of the affected value while some funds had already left Cronos. They do not establish that the remaining amount has since been recovered, nor does restoration of blockchain balances alone demonstrate that every operational consequence has been resolved.

For readers following the incident, subsequent recovery statements need to specify which assets were returned and whether figures describe transfers, restored balances or compensation. Keeping those categories separate is essential to assessing progress without overstating the outcome.

Sources

AI-generated editorial image; not a photograph of the reported event. Prepared with AI assistance and source verification.