In the Chainflip hack on Saturday morning, November 21, 2026, an attacker emptied the Ethereum vault of cross-chain protocol Chainflip with a single transaction. The haul was 520.2 ETH, 3.25 million USDC and about 758,000 USDT, roughly $4.86 million in total. The transaction carried a valid signature from the shared key that the network’s validators manage, so a classic smart contract bug does not appear to be the cause. Chainflip has put the protocol into full safe mode but has not yet confirmed what happened.
What happened in the Chainflip hack
Chainflip is a network for swapping coins between blockchains, such as bitcoin for ether, without creating wrapped tokens. The coins sit in vaults on each chain. On Ethereum, the vault is a smart contract that only pays out when a request carries a valid signature from the network’s shared key.
According to Bitquery’s on-chain investigation, the attack unfolded like this (times in UTC):
- 07:09:59: A newly created wallet receives 0.99 ETH from Tornado Cash, the gas for the next transaction.
- 07:10:59: The same wallet sends a signed batch payout request to the vault. The vault pays its entire ETH, USDC and USDT balance to a second new wallet.
- 07:12 to 07:14: The stablecoins are swapped for ETH on Uniswap, about 2,367 ETH in total. Circle and Tether could have frozen USDC and USDT, but nobody can freeze ETH.
- 07:18 to 07:19: A third wallet pays 2,909 ETH into Tornado Cash in 38 deposits.
Less than ten minutes passed from the first gas payment to the last deposit. Security firm AMLBot described the laundering as highly automated, according to The Block. Decurity’s alert service Defimon flagged the outflow within half an hour.
A valid signature outside the count
Chainflip’s vaults are controlled through a threshold signature scheme (TSS) called FROST. Up to 150 validators each hold a share of the key, and at least 100 of them must take part to produce a signature. No single validator is supposed to know the full key. The validators generate a new key every three days.
Each Ethereum signature also carries a nonce, a number used only once that normally counts up step by step. Bitquery examined all 299,677 signatures the vault has accepted since 2023. The count stood at 314,568 just before the attack. The drain’s signature, by contrast, carried a 39-digit number and is the only one that falls outside the sequence.
That suggests the payout did not come through the network’s normal process and that someone produced a valid signature outside it. Bitquery lists three possible explanations that would look the same on-chain: a stolen key, key shares taken from enough validators, or a flaw that let an invalid signature pass the check. Only Chainflip can say which one applies.
Key rotation and standstill
After the drain, the network kept running normally for almost two hours. The validators signed 63 regular payouts with the same key. At 08:53 UTC, one hour and 42 minutes after the attack, the vault switched to a new key, 13 hours ahead of the next regular rotation according to Bitquery. Chainflip had also rotated early in March and June 2026, though, so the timing alone proves little. Since the switch, the network had produced no further signatures on Ethereum as of Bitquery’s last check at 11:23 UTC.
According to The Block, Chainflip posted on X that it was aware of a potential exploit affecting its vaults and was putting the protocol into full safe mode as a precaution. Deposits, withdrawals, swaps and quoting are disabled. Chainflip has not given a loss figure or a cause so far, and it did not immediately respond to a request for comment from The Block.
Vaults on other chains appear unaffected. Bitquery saw only ordinary payouts from the Arbitrum vault that morning and no spending from the Bitcoin vault address since Friday. Bitquery did not check Solana.
Impact on the FLIP token
Chainflip’s FLIP token fell about 34 percent after the attack, according to The Block. Its market capitalization dropped from about $41.6 million to $27.1 million. The attack comes during an already weak market. As we noted in our crypto update for November 21, bitcoin had briefly fallen below $56,000 earlier.
Whether those affected will be compensated is unclear. For liquidity providers whose funds sat in the Ethereum vault, that is the key question. There is a precedent: on September 12, 2026, an attacker took 736,442 USDT from Chainflip’s Tron vault by getting six withdrawals paid out twice. That time, the cause was how Chainflip processed transaction memos on Tron, a bug in its own code. The validators later voted to reimburse those affected from the protocol’s surplus funds. Chainflip has not yet commented on compensation for the current incident.
What users should keep in mind
- Do not send coins to Chainflip deposit addresses or rely on pending swaps until Chainflip officially announces that safe mode has ended.
- Liquidity providers should rely only on Chainflip’s official channels for information on losses and any compensation.
- Watch out for fake refund or claim sites and direct messages exploiting the incident. Bitquery has already observed address poisoning, with bots sending worthless tokens named ETH from addresses that resemble real ones.
The bigger picture
The case highlights a weakness that smart contract audits rarely catch. The vault did exactly what it was built to do: it executed a request with a valid signature. Security therefore rests entirely on the signing infrastructure behind it, meaning the custody of key shares, the signing ceremony processes and the verification logic. As with the Binance hack in late October, it also shows how quickly attackers move stablecoins into assets that cannot be frozen. Here it took minutes.
For teams running their own threshold-signature vaults, one simple control suggests itself: payouts whose nonce does not fit the expected count should trigger an alert or be blocked. Solid lessons, however, can only be drawn once Chainflip explains how the valid signature came about. Until then, any statement about the cause remains speculation.




