Cross-chain DeFi protocol suffers $10.7M exploit

TLDR

Cross-chain DEX THORChain (RUNE) suffered about $10.7 million in losses after a malicious validator exploited a flaw in its GG20 signing system, triggering an automatic network halt.

1. A newly added node operator reconstructed a vault private key via a GG20 threshold signature weakness and drained roughly $10.7 million from one THORChain vault, while safeguards stopped further losses.
2. THORChains ADR028 recovery plan proposes using protocol-owned liquidity first and then synthetic asset holders to absorb losses, while explicitly avoiding new RUNE minting or token sales.
3. The incident highlights structural risks in cross-chain infrastructure and puts THORChains patched GG20 design, governance response, and future security upgrades under close scrutiny.

Deep Dive

1. How The $10.7M Exploit Happened

According to THORChains post-mortem and multiple reports, a newly churned node operator joined the validator set and exploited a vulnerability in the GG20 threshold signature scheme securing THORChain vaults. GG20 is meant to split signing power across nodes so no single party can reconstruct the private key, but a flaw allowed progressive key material leakage, letting the attacker piece together a full key and drain about $10.7 million from one vault.

Automatic solvency checks detected abnormal outflows within minutes and halted signing and trading across connected chains, and node operators coordinated a full network halt and patch deployment within roughly two hours, preventing additional vaults from being drained. A detailed breakdown appears in THORChains published post-mortem and the linked coverage of the exploit and GG20 flaw.

2. Who Eats The Loss And What Changes

THORChain governance is voting on ADR028, a recovery plan that would prioritize protocol-owned liquidity to cover losses, then spread any remaining shortfall across holders of synthetic assets that track BTC, ETH and others on THORChain, as described in the ADR028 coverage. The plan explicitly rules out minting or selling new RUNE to plug the hole, which avoids direct dilution of existing RUNE holders but depletes protocol reserves.

Because the loss is concentrated in protocol capital and synth claims on the system, user wallets and core LP positions are not directly hacked, but they may feel indirect effects through reduced liquidity, tighter pool conditions or changes to synth pricing once trading resumes.

3. Broader Cross-Chain Risks And What To Watch

Security researchers have criticized THORChains decision to keep GG20, even in patched form, arguing that the design has brittle assumptions and is hard to reason about, while others note that the automatic halt mechanisms worked as intended. This exploit lands in a broader pattern of bridge and cross-chain hits where relatively small design mistakes or validator compromises have led to eight-figure losses across protocols this year.

Key things to watch are: completion and external review of GG20 patches, the outcome of the ADR028 vote, any bounty-driven recovery of funds, and whether THORChain tightens node onboarding and monitoring requirements to reduce insider or rogue-validator risk.

Conclusion

A sophisticated insider-style attack on THORChains GG20 signing scheme turned into a $10.7 million loss but also demonstrated that its automated solvency checks and emergency halts can contain damage once an exploit begins. The recovery path shifts pain toward protocol reserves and synthetic asset holders instead of RUNE dilution, while the governance and technical response will shape how much confidence users and institutions place in THORChain and cross-chain DeFi infrastructure going forward.