
Cross-chain swap protocol Chainflip has given the person who drained its vaults until Monday evening to send most of the money back — or face a full law-enforcement chase. The offer is blunt: return 90% of the roughly $12 million taken on Saturday, keep the other 10% as a bounty, and the whole thing gets filed as a white-hat recovery.
The deadline is 18:38 UTC on Monday, November 23 — less than a day away. If the funds arrive in time, Chainflip says it will ask no further questions and withdraw the reports and complaints it has already filed with law enforcement. If they don’t, the company says it will pursue the case as hard as it can, for as long as it takes.
How the vaults were drained
The attack began in the early hours of Saturday, November 21. A single transaction at 07:10:59 UTC emptied Chainflip’s Ethereum vault of every unit of ETH, USDC and USDT it held — 520.22 ETH, 3.25 million USDC and 758,141 USDT — in under ten minutes. At first the damage looked contained at about $4.86 million.
It wasn’t. Later that day Chainflip confirmed the attacker had also taken 122.86 BTC from its vaults, pushing the total to roughly $12 million. Bitcoin made up the biggest share of the haul, worth around $7.4 million at the weekend’s prices.
What makes this breach different from a typical smart-contract exploit is that nothing appears to have been coded wrong. The withdrawal carried a valid signature, and the evidence points to a copied shared signing key for the validator network rather than a bug in the protocol’s code. Whoever did it didn’t break the vault door — they appear to have had a copy of the key.
Chainflip says its investigation traced the preparation back over ten days: funding moved through the Tornado Cash mixer on November 11, followed by a FLIP token purchase and the registration of a validator account on November 20, the day before the attack. The company says it has collected identifying information tied to that validator account and the server behind it, and that it has identified how the key was exposed and taken steps to stop it happening again. It has not published a detailed post-mortem yet, and it has not explained publicly how the key leaked in the first place.
Since Saturday morning the protocol has been in full Safe Mode. Deposits, withdrawals, swaps and quotes are all disabled, and Chainflip has not yet said what happens to swaps that were in flight when it shut down, or whether affected users will be compensated.
The $1.2 million offer — and the Monday deadline
The terms are published on Chainflip’s own page addressed to the attacker: return 90% of what was taken, keep 10% — roughly $1.2 million — and walk away with the incident recorded as a white-hat recovery. The Bitcoin leg of the deal is precise: 110.57523337 BTC, exactly 90% of the Bitcoin stolen, to a designated return address, with the Ether leg covering the converted value of the rest.
As of Sunday, no return of funds had been confirmed. The offer is a gamble on both sides. For Chainflip, it is the only realistic path to getting the money back: with the signing key compromised, the protocol has no insurance fund, no on-chain recovery mechanism and no way to freeze or claw back funds once they have moved. For the attacker, it trades a $1.2 million payday for walking away clean — but only if both payments land before the deadline.
The market has already delivered its verdict on the protocol. Chainflip’s native FLIP token fell about 43% in the day after the attack, before clawing back some ground toward $0.33. That is a steep drop even in a week when the whole market is down — Bitcoin itself fell to $55,130 on Saturday before recovering to around $60,700 on Sunday.

What happens to users’ money
That is the question Chainflip has not answered yet. The company has announced no reimbursement plan for this hack, and the scale makes that a much harder promise than last time. In September, a smaller exploit drained 736,442 USDT from Chainflip’s Tron vault, and affected users were repaid. Twelve million dollars is a different order of magnitude, and the bounty-first approach suggests the protocol is hoping to recover the funds from the attacker before committing to compensation.
Anyone with a swap in flight when the protocol went into Safe Mode is still waiting to learn whether their trade will be executed or refunded. Until Chainflip says otherwise, those funds sit in limbo alongside the protocol itself.
A second breach in ten weeks
This is the second time in about ten weeks that Chainflip’s vaults have been drained. The September incident was smaller and contained; this one took the protocol’s Bitcoin, Ether and stablecoin vaults in a single morning. Two breaches in quick succession raise an awkward question about the design the protocol was built on: its own security pages previously claimed no single entity ever controls user funds during a swap, yet a single compromised signing key was enough to empty the vaults.
Whether the key was stolen, leaked or sold, the post-mortem — when it arrives — will have to explain how the shared key ended up in the wrong hands, and what has actually changed to stop it happening a third time. Until then, the clock is the story. Monday at 18:38 UTC decides whether this ends as a negotiated return or a long law-enforcement chase, with $12 million of user funds hanging on the answer.