Chainflip Reports $12M Loss as Ethereum Vault Drain and Bounty Terms Raise Questions

Daily Feed
Chainflip Reports $12M Loss as Ethereum Vault Drain and Bounty Terms Raise Questions

Chainflip says an attacker stole about $12 million from its cross-chain vaults on November 21. Blockchain analysis traces $4.86 million leaving the Ethereum vault, but the unusual signing activity behind that withdrawal, and the larger reported loss, remain only partly explained.

What was taken from Chainflip?

Chainflip lets users swap native assets across blockchains. Its vaults hold assets such as Bitcoin and Ether, while validators coordinate the signatures required to authorize withdrawals.

Chainflip’s reported breakdown of the November loss was 122.86137042 BTC, 520.2243399 ETH, 3, 249, 631.41 USDC and 758, 141.33 USDT. The company valued the combined loss at approximately $12 million.

Bitquery’s on-chain analysis traces one specific part of that reported total: $4.86 million in ETH, USDC and USDT leaving Chainflip’s Ethereum vault. That figure covers assets traced out of the vault. It is not an independent audit of the wider loss or the reported Bitcoin theft.

USDC and USDT are stablecoins, cryptocurrencies designed to track the value of another asset, usually the U.S. dollar. Their inclusion in the vault loss does not mean the stablecoin systems themselves were compromised.

A valid signature, with an unusual nonce

Bitquery says the Ethereum vault accepted a valid signature for the withdrawal, meaning the vault’s authorization check passed. That does not show whether the attacker stole a key, compromised enough validator key shares, or exploited a flaw in signing or verification.

Bitquery says the request included an anomalous signing nonce, a number associated with a signing request rather than the ordinary transaction counter used by an Ethereum account. Its analysis found that the vault had accepted 299, 677 signatures over three years, and the drain was the only one outside the running nonce count. The nonce was 39 digits long.

The unusual value offers a forensic clue, but it does not prove how the attacker gained authorization. Bitquery lists several possible explanations, including a stolen key, compromised validator shares, or a flaw that let an improper signature pass. Its analysis does not establish which explanation is correct.

Bitquery says the relevant setup uses FROST, a threshold-signature scheme. According to its account, at least 100 of 150 validators must participate to produce a signature. Threshold signing lets a group authorize a transaction without any one validator holding the complete key. That leaves several possible ways the signing process could be compromised.

Chainflip reportedly said, “We have identified the mechanism of key exposure, ” and had taken steps to block the same method. The technical details available so far are not enough to assess exactly what failed or how the fix addresses it.

How the funds moved

Bitquery traced a wallet that received gas funds from Tornado Cash one minute before the Ethereum vault drain. The assets then moved to another wallet, where USDC and USDT were exchanged for Ether through Uniswap within four minutes.

Bitquery says a third wallet deposited a total of 2, 909 ETH into Tornado Cash in 38 transactions across three batches. Those funds were part of the Ethereum vault loss already counted, not an additional theft.

Tornado Cash is a cryptocurrency mixer, a service designed to make links between incoming and outgoing transactions harder to follow. The transaction trail shows funds moving into the mixer, but it does not identify who controlled the wallets or establish the attacker’s identity.

The 10% offer has an unresolved mismatch

Chainflip reportedly told the attacker: “Keep 10% as a bounty and return 90%.” The offer set a deadline of 18:38 UTC on November 23. The company reportedly said it would treat a qualifying return as a white-hat recovery, ask no further questions, and withdraw reports and complaints filed with law enforcement.

The reported repayment instructions requested 110.57523337 BTC and 2, 618.1 ETH. The Bitcoin amount is roughly 90% of the reported 122.86137042 BTC loss. The requested Ether amount, though, is far greater than the reported 520.2243399 ETH stolen.

No explanation for the discrepancy is available. The stated terms also do not show how the requested amounts add up to a 90% return across all four assets. For now, the offer is best described as a reported 10% bounty, not a confirmed $1.2 million payment. A precise dollar value would require a valuation time and a reconciled calculation, neither of which is established by the reported figures.

Available reporting does not confirm whether the attacker accepted the offer or returned any funds. A bounty can be a practical recovery tool, but unclear repayment math makes it harder for users and observers to understand what the deal required.

September’s Tron exploit was a different failure

Chainflip also reported a separate exploit of its Tron USDT integration on September 12. The company said its system used transaction memos to interpret swap instructions. In the exploit it described, validators had already signed a transaction when the attacker attached a memo. The system treated the memo as a separate swap and issued another payout against the same underlying transaction.

Chainflip reported six unauthorized payouts totaling 736, 442.17 USDT. The company said the attacker tried the technique eight times over about 90 minutes. Eight attempts and six payouts are separate counts. Chainflip temporarily suspended operations while it investigated and prepared an update, then outlined network upgrades and adjustments to affected liquidity-provider balances.

That incident involved how Chainflip handled transaction metadata on its Tron integration. It should not be confused with the November Ethereum vault signature anomaly or treated as evidence that Tron’s network or USDT itself was compromised.

Key questions and answers

  • How much did Chainflip report losing?

    Chainflip put the November loss at approximately $12 million across BTC, ETH, USDC and USDT. Bitquery traced $4.86 million leaving the Ethereum vault, but that analysis does not independently verify the broader total.

  • How did the attacker authorize the Ethereum withdrawal?

    The vault accepted a valid signature with an anomalous signing nonce. The available evidence does not show how the attacker obtained or used the signing capability.

  • Was the reported bounty worth $1.2 million?

    Chainflip reportedly offered the attacker 10% for returning 90%, but neither the dollar value nor the repayment calculation is clearly established. The requested 2, 618.1 ETH also exceeds the reported 520.2243399 ETH loss.

  • Were the November funds returned?

    No return is confirmed in the reporting available here. Chainflip’s reported offer set a November 23 deadline, but its outcome is unknown.

  • Was the September Tron exploit the same vulnerability?

    No evidence connects the incidents. Chainflip described the September issue as a transaction-memo flaw in its Tron integration. The November incident involved an accepted Ethereum vault signature with an unusual nonce.

The on-chain trail shows in detail how the Ethereum funds moved, but the authorization failure remains unresolved in public. The next meaningful test is whether Chainflip can publish enough technical detail for users to assess the fix and reconcile the reported losses with the bounty terms.

Further reading

Share this article

Powered by ADBYTES

Advertise smarter.

Adbytes.Media is a transparent advertising network where advertisers reach real audiences and publishers, affiliates & everyday members earn ADBYTES tokens. Join the community and start earning today.

Back to Blog