analysis · Security · Chainflip · Ethereum

Chainflip's Ethereum vault lost $4.86 million. The signature was valid.

An on-chain investigation traces one anomalous, signed withdrawal. The mechanism and customer impact await Chainflip's account.

Observed November 21, 2026 at 1:00 PMBlue Rogues Newsroom
Chainflip's Ethereum vault lost $4.86 million. The signature was valid. — Blue Rogues Crypto editorial artwork
Blue Rogues editorial artwork · BRC-20261121-002

On November 21, a single transaction emptied the ETH, USDC and USDT held in Chainflip's Ethereum vault, according to Bitquery's on-chain investigation. The firm valued the transfer at about $4.86 million at the time. Chainflip said on November 21 that it was investigating a possible exploit affecting its vaults and had placed the protocol in full safe mode, disabling deposits, withdrawals, swaps and quoting. Its website displayed a notice that services were temporarily unavailable when we checked around 13:00 Brasília time.

The distinguishing detail is the signature. The withdrawal carried a valid signature from the key used to authorize vault payouts. Bitquery says its nonce, a number that prevents reuse of signed requests, broke the normal running sequence. In its review of 299,677 accepted signatures since 2023, it found this one anomalous request. The vault accepted it and paid.

Bitquery traced the USDC and USDT through swaps into ETH and then 2,909 ETH into Tornado Cash within minutes. That describes the route after the withdrawal. It does not identify the person behind it or make the mixer the cause of the breach.

What the evidence does not settle

A valid signature does not by itself prove that the aggregate key was stolen. An attack on enough signing shares, abuse of a signing workflow, or a validation flaw could produce different explanations for the same on-chain result. Bitquery explicitly says it cannot establish which occurred. At publication preparation time, we found no Chainflip report establishing a root cause or specifying the effect on individual customer balances.

Our read

Cross-chain systems must authorize real assets to leave vaults. Here the control accepted an instruction that looked cryptographically valid while the transaction appeared outside the ordinary sequence. The immediate questions are how the instruction was produced, how quickly other vaults were contained, and how any affected liquidity providers or users will be accounted for. Those answers require a Chainflip incident report and follow-up evidence, not an inference from wallet movement alone.

This is a developing incident. We will update the account when the project publishes findings on cause, scope, service restoration and recovery.

Sources: Bitquery investigation; Chainflip service notice; Chainflip governance and safe mode documentation.