Mentioned in This Article
1. Chainflip hack drains the protocol's Ethereum vault
Chainflip, a decentralized protocol for swapping assets between blockchains, lost approximately $4.86 million on November 21, 2026, when an attacker drained its Ethereum vault in a single transaction. The Chainflip hack took 520.2 ETH, 3.25 million USDC and 758,000 USDT, and about 2,909 ETH was routed into the Tornado Cash mixer roughly nine minutes later.
Initial estimates of the loss were closer to $4 million. A more complete tally, once the value of the ether was added to the two stablecoins, brought the total to about $4.86 million.
The withdrawal carried a valid signature from the vault's own aggregate key, which points to a compromise of the protocol's signing key rather than a flaw in its smart contract code. Chainflip paused its core services, including swaps, while it investigates. The project's native token, FLIP, fell about 39% after the breach became public.
2. What is Chainflip?
Chainflip is a decentralized exchange protocol designed to let users swap native assets across different blockchains, for example exchanging ether on Ethereum for an asset on another network, without relying on a centralized exchange or wrapped tokens.
To make those swaps possible, the protocol holds pools of assets in vaults on each supported chain. When a user swaps into an asset, the corresponding vault pays it out. Those vaults are controlled not by a single company wallet but by a network of independent validators that jointly authorize every withdrawal.
That design is intended to remove any single point of failure. The Ethereum vault at the center of this incident held the protocol's ether and its two major dollar-pegged stablecoins, which is why all three assets left in the same transaction.
Cross-chain protocols of this type have become important infrastructure in crypto because users increasingly hold assets on several networks and want to move between them directly. The same role makes them attractive targets, since their vaults must hold meaningful liquidity on every chain they support.
3. How did the Chainflip hack happen?
The attacker emptied the Ethereum vault with one transaction that was authorized by a valid Schnorr signature from the vault's aggregate key, also known as its TSS key. In practical terms, the vault's smart contract received a correctly signed instruction to release the funds, and it carried out that instruction as it was built to do.
TSS stands for threshold signature scheme. Under this approach, a signing key is split into pieces held by different parties. A transaction can be signed only when enough of those parties cooperate, so no individual holder can move funds alone. Schnorr signatures are a type of digital signature that allows multiple contributions to be combined into one compact signature that the blockchain verifies like any other.
Because the signature checked out, the leading explanation is that the signing key itself was compromised. The contract appears to have functioned correctly; the problem lies with whoever was able to produce the authorization. Chainflip has not yet published findings explaining how a valid signature came to be generated for the attacker's withdrawal.
4. Breaking down the $4.86 million loss
The stolen funds came from three separate assets held in the same vault. The largest portion by value was in stablecoins: 3.25 million USDC and 758,000 USDT, together worth a little over $4 million because both tokens are designed to hold a value of one US dollar each.
The remainder was 520.2 ETH. At the ether prices prevailing on the day of the attack, that holding accounted for the gap between the early estimate of about $4 million and the fuller figure of approximately $4.86 million. Early reports appear to have focused on the stablecoin outflows before the value of the ether was included.
The amount that later reached Tornado Cash, about 2,909 ETH, is far larger than the 520.2 ETH taken directly from the vault. The difference reflects the attacker's decision to convert most of the stolen stablecoins into ether before sending the proceeds to the mixer, so the figure that entered Tornado Cash represents most of the haul expressed in a single asset.
5. Nine minutes from the vault to Tornado Cash
Speed defined what happened next. Shortly after the withdrawal, the attacker swapped most of the stolen USDC and USDT into ether. About 2,909 ETH then flowed into Tornado Cash, roughly nine minutes after the theft.
Tornado Cash is a mixing service on Ethereum. Users deposit funds into a shared pool and later withdraw them to a different address, which breaks the visible link on the blockchain between where money came from and where it ends up. That makes it far harder for investigators to follow stolen assets to an exchange or other point where they might be identified.
The conversion into ether before mixing was not incidental. Circle and Tether, the companies that issue USDC and USDT, have the technical ability to freeze tokens held at specific addresses. A thief holding stablecoins risks having them locked before they can be moved. Ether has no issuer with that kind of control, so swapping out of the stablecoins quickly removed the chance of a freeze before anyone could act.
6. Chainflip pauses the network
Chainflip said it was aware of a potential exploit affecting its vaults and halted core services, including swaps, while the investigation continues. Pausing the network prevents further withdrawals and gives the team time to assess the damage and secure the remaining infrastructure.
For users, the pause means swaps through the protocol are unavailable until Chainflip decides it is safe to resume. Liquidity providers, who supply the assets held in the vaults, are also waiting to learn how the loss will be handled.
A pause of this kind is a standard defensive step for decentralized protocols after a suspected breach. It does not recover lost funds, but it limits the risk that the same weakness is used again while the cause is still unknown. Until the team understands how the signing key was used without authorization, reopening the vaults would expose any remaining assets to the same threat.
The market reacted quickly. FLIP dropped about 39% after news of the breach spread, a sharp repricing that reflects both the direct loss and investors' concerns about the protocol's security.
7. A second security incident in 2026
This is not Chainflip's first serious security problem this year. In September 2026, an earlier exploit drained funds from the protocol through a series of coordinated withdrawals from its liquidity pools.
Two significant losses within a few months are the kind of pattern that users and liquidity providers notice. Each incident on its own might be treated as a setback; together, they raise broader questions about how the protocol manages risk.
For a cross-chain swap service, trust is central to the business. Liquidity providers deposit assets only if they believe those assets are safe, and users route swaps only through protocols they consider reliable. Repeated incidents make both groups more cautious.
8. Why a key compromise is harder to fix than a code bug
The suspected cause of this breach matters for what comes next. When an exploit stems from a smart contract bug, the remedy is relatively well defined: developers patch the code, commission a fresh audit and redeploy. The issue is technical and contained.
A compromised signing key is a different kind of problem. It raises questions about people, processes and infrastructure: who held the pieces of the key, how they were stored and protected, and how an attacker obtained enough access to produce a valid signature. In a threshold scheme, that includes the validators and operators who each hold a share.
Answering those questions can require changes to operational security rather than just software, and those changes are harder for outsiders to verify. If the key compromise explanation is confirmed, Chainflip will need to explain clearly what went wrong and describe how its key management will change to prevent a repeat.
9. What it means for FLIP holders and users
For FLIP holders, the most immediate consequence is the roughly 39% decline in the token's price. The longer-term question is whether confidence in the protocol can be restored after two incidents in the same year.
For users and liquidity providers, the key issues are how long the pause will last and how the protocol will address the missing funds. Those answers will shape whether activity returns once swaps resume.
The broader lesson extends beyond Chainflip. Cross-chain protocols concentrate large amounts of value in vaults on several networks, and the mechanisms that authorize withdrawals from those vaults are among the most sensitive parts of their design. When the authorization layer fails, even a correctly working smart contract cannot stop the loss.
Incidents like this also show how quickly stolen value can move once an attacker controls an authorization path. In this case, the window between the vault being emptied and the funds entering a mixer was measured in minutes, leaving little time for any outside party to intervene. That speed places even greater weight on preventing unauthorized signatures in the first place, since the opportunity to stop funds after they leave can be extremely short.
10. What to watch next
Three developments will determine how this incident is judged. The first is Chainflip's post-incident report, which should explain how the signing key was compromised and what was done to close that gap.
The second is when and how the protocol ends its pause and restores swaps, including any changes to its security setup before it reopens.
The third is whether any of the roughly 2,909 ETH sent through Tornado Cash can be traced as it leaves the mixer. Funds that exit a mixer must eventually be moved or cashed out somewhere, and investigators often watch for those movements in the days and weeks after an exploit.
