T
iTokenly

Tectonic (TONIC collateral) hack — August 2026

Verified — 7 sourcesLast checked September 10, 2026

Incident facts

Date of incident
Target typeLending protocol
Loss$120,400,000Price at time of incident
Recovered$111,200,000
MethodOracle or price manipulationThe thinly traded TONIC token was pumped roughly a hundredfold in about twenty minutes, deposited as collateral at its inflated price, and borrowed against across nine markets for the protocol's stablecoin and blue-chip reserves
ChainsOther
OutcomePartially recovered

What happened

Cronos, the Crypto.com-linked network, halted its entire blockchain on 30 August 2026 after an attacker drained Tectonic, its largest lending protocol.

No contract was broken. TONIC, Tectonic's own token, carried a 20% collateral factor and traded thinly enough that the attacker could raise its price roughly a hundredfold inside twenty minutes. About ten minutes later a single transaction borrowed $120.4m across nine Tectonic markets against the inflated collateral, which is the figure in Cronos's own post-mortem. The withdrawals covered roughly $54.32m in USDC, $44.87m in USDT, 95.36 WBTC, 1,861 WETH and 39.61m CRO, alongside smaller tokens. Before the attack Tectonic held about $121.7m in total value locked and $82.7m in active loans.

What happened next is the part worth recording. Cronos did not negotiate and did not wait. The malicious activity was identified about 36 minutes in; validators halted the chain at block 90,907,150, restored its state to block 90,896,188, the last block before the attack, and discarded 10,961 blocks, about one hour and fifty-four minutes of history. Production resumed from block 90,896,189 at 23:49:01 UTC on 30 August, about eleven hours after the attack began. Cronos called it a validator-consensus emergency action to protect users. The theft was erased from the ledger along with every other transaction anyone had made in that window, which is the cost of the remedy and the reason it remains contested: the balances of users who had nothing to do with the attack were rewound too, and open positions on live applications were repriced when trading resumed.

The rollback reversed about $111.2m, which is recorded as recovered rather than netted off the headline. It could not reach the $9.19m, 7.6% of the total, that had already left the network before the halt. Earlier reporting identified 2,592.2152 ETH, about $6.29m, bridged to Ethereum in that window, part of which the attacker later began moving on to Bitcoin; the post-mortem's larger figure covers everything that got out. It does not name the attacker or say who will absorb the unrecovered amount.

The figure first recorded here was $75m, an on-chain researcher's same-day estimate of attacker-controlled assets. It was replaced on 10 September by the post-mortem's $120.4m, which matches CertiK's earlier impact figure; Foresight News had counted $119.5m. The DefiLlama dataset lists $124.47m, which neither Cronos nor any publisher supports, and it is not followed here.

Sources

  1. The BlockSecondary · retrieved 2026-09-10
  2. The DefiantSecondary · retrieved 2026-09-10
  3. CoinDeskSecondary · retrieved 2026-09-10
  4. The Crypto TimesSecondary · retrieved 2026-09-10
  5. The Block, on the Cronos post-mortemSecondary · retrieved 2026-09-10
  6. CoinDesk, on the Cronos post-mortemSecondary · retrieved 2026-09-10
  7. crypto.newsSecondary · retrieved 2026-09-10

Changes to this entry

  • Recorded the day after the incident, while it was still developing and neither Tectonic nor Cronos had confirmed a figure. The $75m is an on-chain researcher's estimate of attacker-controlled assets; Foresight News counted $119.5m of total pool outflows, a different quantity. Both will be corrected against the protocol's own accounting when it is published.
  • Outcome changed from unresolved to partially recovered and $68,700,000 recorded as recovered. Cronos validators restored the chain state to before the attack, discarding 10,961 blocks and about 1 hour 54 minutes of history, and resumed from block 90,896,189 at 23:49:01 UTC on 30 August 2026. That reversed roughly $68.7m; the $6.29m already bridged to Ethereum as 2,592.2152 ETH was beyond its reach and remains lost. The headline still records what was taken, per the methodology, with the reversal recorded separately rather than netted off. CertiK's $120.4m impact figure was also added to the summary alongside Foresight News's $119.5m, both measuring total pool outflows rather than attacker-held assets.
  • Amount changed from $75,000,000 to $120,400,000 and the recovered figure from $68,700,000 to $111,200,000, following Cronos's post-mortem of 8 September: $120.4m borrowed across nine markets, about $111.2m reversed by the rollback, and $9.19m (7.6%) that had left the network beyond its reach. The $75m was an on-chain researcher's same-day estimate of attacker-controlled assets; the post-mortem figure matches CertiK's. The downtime was previously given as roughly twenty-two hours; the post-mortem puts the resumption about eleven hours after the attack began, and the summary is corrected. DefiLlama's $124.47m is supported by neither Cronos nor any publisher and is not followed.

Cite this

This data is published under CC BY 4.0. You may reuse it, including commercially, as long as you credit iTokenly and link back.

iTokenly Hack Registry, "Tectonic (TONIC collateral) hack — August 2026", iTokenly, accessed 2026-10-15, https://itokenly.com/hacks/tectonic-tonic-collateral
https://itokenly.com/hacks/tectonic-tonic-collateral

Permalinks never change. If an entry is renamed, the old address keeps working.

Spotted an error? Write to [email protected]. Corrections to published figures are logged on this page. See the methodology for how entries are checked.