Chainflip Freezes Swaps After $4.86 Million Ethereum Vault Drain
• November 22, 2026 11:14 am • CommentsChainflip has frozen its cross-chain swap protocol after nearly $4.9 million in crypto left the project’s Ethereum vault in a single transaction.
The shutdown is broader than the Ethereum vault that was drained. Deposits, withdrawals, swaps and price quotes were all disabled, leaving users and liquidity providers waiting for the protocol to exit its emergency “full safe mode.”
Chainflip confirmed the potential exploit in a public update and said the restrictions were precautionary while its investigation continued.
We’re aware of a potential exploit affecting Chainflip vaults.
As a precaution, the protocol is being put into full safe mode. Deposits, withdrawals, swaps and quoting are disabled.
We’re investigating and will share updates here as we learn more.
— CHAINFLIP (@Chainflip) November 21, 2026
Bitquery’s onchain investigation traced the incident to a transaction at 07:10:59 UTC on November 21. The transfer removed about 520.2 ETH, 3.25 million USDC and 758,141 USDT—the vault’s entire liquid balance at that moment.
The stablecoins were quickly traded for ETH. Bitquery found that 2,909 ETH then entered Tornado Cash through 38 deposits, with the trail moving from the initial gas funding to the mixer in under ten minutes.
That speed mattered. Circle and Tether can freeze their dollar-backed tokens, but once the assets had been converted to ETH and deposited into a mixer, the recovery picture became much harder.
The first onchain alert quantified the assets swept from the vault and identified the signing-key system as the focus of the early investigation.
🚨 @Chainflip – Loss $4.86M (2026-11-21)
Network: Ethereum
Type: Private Key Compromise (aggregate/TSS signing key)
The Chainflip Vault was swept of its entire liquid balance — 520.2 ETH, 3.25M USDC and 758K USDT (~$4.86M) — to a fresh single-tx EOA (0x7d14…1eaf). The drain…
— Defimon Alerts (@DefimonAlerts) November 21, 2026
The vault did not reject the withdrawal as an invalid request. According to Bitquery, the key contract accepted its signature as valid—but the transaction carried a 39-digit nonce that broke sharply from the normal sequential count used across hundreds of thousands of prior signatures.
That points investigators toward the signing process rather than a routine user-side failure. A leaked key, enough compromised validator shares, or a flaw that allowed a bad signature to pass could produce similar onchain evidence.
The blockchain record does not identify which explanation is correct.
CryptoSlate reported that the emergency pause also affected routes that never touched the drained Ethereum vault directly. A Bitcoin-to-Solana swap, for example, still depends on the shared protocol to recognize the incoming deposit and authorize the outgoing payment.
The swap and liquidity-provider apps remained in maintenance mode during the outlet’s check, and no restart time was posted. Deposits awaiting final confirmation were left pending until Chainflip could safely resume protocol operations.
The report also noted that Chainflip’s Arbitrum payouts appeared ordinary during the reviewed period, while the Bitcoin vault address showed no spending after Friday. Solana was outside Bitquery’s review, so those observations did not amount to a clean bill of health for every connected chain.
The practical consequence was still network-wide: users could not complete new swaps, withdraw liquidity or receive quotes while the shared state machine remained paused.
That is the real operational lesson here: a cross-chain network can spread one vault’s security problem across every route that depends on the same signing and settlement machinery.
Chainflip had not published a final root-cause report at the time of writing. Until it does, claims that the team knows exactly how the signature was produced should be treated as hypotheses—not conclusions.
Join the conversation!
We have no tolerance for comments containing violence, racism, profanity, vulgarity, doxing, or discourteous behavior. If a comment is spam, instead of replying to it please click the icon below and to the right of that comment. Thank you for partnering with us to maintain fruitful conversation.
