Chainflip’s Vault Theft Reaches About $12 Million as Attacker Gets a 10% Offer

Key Takeaways
- Chainflip lists 122.86137042 BTC, 520.2243399 ETH, 3.25 million USDC and 758,141 USDT as taken.
- The protocol’s recovery offer asks for 90% back by 18:38 UTC on November 23, with 10% left as a bounty.
- The services were paused in full safe mode; Chainflip has not confirmed a recovery or published a full technical post-mortem.
Chainflip’s latest disclosure has more than doubled the reported scale of Saturday’s vault theft. The cross-chain swap protocol says 122.86137042 BTC, 520.2243399 ETH, 3,249,631.41 USDC and 758,141.33 USDT were taken from its vaults on November 21. Its published terms put a deadline on a proposed recovery: return 90% by 18:38 UTC on November 23 and keep the remaining 10% as a bounty.
The disclosure follows an initial report focused on Chainflip’s Ethereum vault, where a single transaction removed ETH and stablecoins worth about $4.86 million. The added Bitcoin amount, listed separately by Chainflip Labs, makes this a wider incident than that first figure suggested. The company has not published a single combined dollar valuation on its terms page; the commonly reported roughly $12 million total is an estimate based on asset prices.
What Chainflip says was taken
Chainflip Labs’ message dated November 21 lists four amounts: 122.86137042 BTC, 520.2243399 ETH, 3,249,631.41 USDC and 758,141.33 USDT. The ETH and stablecoin figures match the Ethereum-vault transfer described in early reporting. The BTC figure expands the disclosed scope beyond that Ethereum transaction.
Those are quantities, not a fixed dollar loss. Bitcoin and ether prices move, while USDC and USDT are designed to track the U.S. dollar but can trade away from it. Reports have rounded the combined value to around $12 million; Chainflip’s statement itself does not provide a total in dollars.
Why the first estimate was smaller
The first widely reported figure reflected the visible Ethereum-side drain: roughly 520 ETH, 3.25 million USDC and 758,000 USDT. The transaction carried a valid signature accepted by Chainflip’s vault, according to the on-chain analysis reported by The Block and CoinDesk. That fact establishes that the vault accepted the authorization; it does not, by itself, explain who produced the signature or how.
Blockchain analytics firm Bitquery examined the Ethereum records and reported that the transaction’s nonce was an outlier against the running sequence it observed. Bitquery said the drain was the only one of 299,677 accepted signatures it reviewed that broke that count. The firm cautioned that on-chain evidence alone cannot determine whether key material was stolen, enough validator shares were compromised, or another failure occurred. Chainflip now says it has identified the mechanism of key exposure, but it has not yet published a technical post-mortem explaining it.
The 10% recovery offer
Chainflip’s public message asks for 110.57523337 BTC and 2,618.1 ETH to be returned by 18:38 UTC on November 23. If both amounts arrive before the deadline, the company says it will treat the outcome as a white-hat recovery, ask no further questions and withdraw its reports and complaints to law enforcement.
This is an offer to the holder of the stolen assets, not a reimbursement plan for users. It does not guarantee that funds will be recovered, and as of publication there is no confirmation that the attacker has accepted or returned anything. The recovery terms also do not say how Chainflip would compensate affected liquidity providers if the offer fails.
The deadline is imminent, so readers should distinguish the published terms from an outcome. Until Chainflip confirms a return, the assets remain reported stolen and the bounty remains only a proposal.
What the protocol has said about the response
Chainflip’s first public notice said it was aware of a potential exploit and had placed the protocol in “full safe mode.” The notice said deposits, withdrawals, swaps and quoting were disabled as a precaution. The later return page says the team traced preparation to Tornado Cash funding on November 11, a FLIP purchase, and a validator account registered on November 20. These are the company’s assertions; it has not released supporting technical details in a post-mortem.
The Block and CoinDesk reported that the Ethereum-side stablecoins were converted into ether and that most of the funds moved through Tornado Cash within minutes. Bitquery’s analysis likewise traced about 2,909 ETH into Tornado Cash. That fast movement illustrates why a blockchain transfer can be public while the identity behind an address remains unknown, and why recovery is difficult once assets pass through a mixing service.
What users should do while services are paused
Chainflip’s notice explicitly disabled deposits, withdrawals, swaps and quotes. Users should not assume a transaction can complete or that funds can be withdrawn until the protocol announces a restart through its official channels. Avoid unsolicited “recovery” services, claim links or requests to connect a wallet or sign a message: the company’s published offer is directed to the attacker and is not a user claim process.
The public information reviewed for this article does not establish the status of every individual pending swap or provide a timeline for reopening. Nor has Chainflip published a compensation commitment for this incident. The earlier September loss from the protocol’s Tron vault was a separate event; The Block reported that validators later approved reimbursement in that case, but that precedent is not a promise about this larger incident.
The larger security question
Cross-chain protocols hold assets in vaults on multiple networks and depend on authorization systems to release them. Threshold signing can distribute control across validators, but it does not eliminate risk if the signing process or key material is compromised. In this incident, the Ethereum vault accepted a valid signature; the exact failure mechanism is not independently documented in a public technical report yet.
That distinction matters. Calling an incident a smart-contract exploit can imply the contract logic itself was defective, while an accepted signature may point to a different layer of the system. At present, the strongest careful account is that Chainflip reports key exposure, independent analysts observed an unusual authorization pattern on Ethereum, and the precise technical pathway awaits a fuller explanation.
What remains unknown
The public record does not yet show whether the attacker will meet the November 23 deadline, whether any assets have been recovered, or when Chainflip will leave safe mode. There is no published technical post-mortem detailing the key-exposure mechanism, and no confirmed plan for user losses. Those are the facts that will determine whether the bounty changes the outcome or simply marks the end of an attempted negotiation.
For now, Chainflip has disclosed a broader set of stolen assets and put concrete terms on a possible return: 90% back, 10% kept, by a stated UTC deadline. Until the company confirms funds have arrived and services have resumed, users should treat the protocol as paused and the recovery as unresolved.
DISCLAIMER
This article is for informational purposes only and does not constitute financial advice. Cryptocurrency investments involve substantial risk and extreme volatility - never invest money you cannot afford to lose completely. The author may hold positions in the cryptocurrencies mentioned, which could bias the presented information. Always conduct your own research and consider consulting a qualified financial advisor before making any investment decisions.









