Drift Hack: $61M in ETH Sent to Tornado Cash10 min read2,020 words

Drift Hack: $61M in ETH Sent to Tornado Cash

A wallet linked to Drift’s $295M hack moved $61M in ETH to Tornado Cash. Here’s what the transfer means for tracing, recovery and affected users.

Drift hackTornado CashDrift Protocol exploitDeFi securitycrypto fund recovery
Drift Hack: $61M in ETH Sent to Tornado Cash

$61 Million in ETH Moves After the Drift Hack. What Happens Next?

A wallet linked to the Drift Protocol exploit moved about $61 million in Ether to Tornado Cash, putting fresh spotlight on a hack that reportedly caused around $295 million in losses. Lookonchain said the transfers came after roughly two months of inactivity. Arkham estimates that the addresses tied to the exploiter still held about 81,454 ETH, worth roughly $194 million.

That transfer matters - but it doesn't settle the big questions. Sending funds to a mixer can make it harder to connect deposits to later withdrawals, but it doesn't erase the public transaction record, confirm a cash-out, or prove what affected users will ultimately be able to recover.

For Drift users, the next point of interest is how this activity fits alongside the recovery process Drift opened for DFX recovery tokens on October 1. For the broader DeFi market, the takeaway is familiar but worth repeating: security incidents don't end when the breach happens. Funds move, attribution gets refined, and recovery systems have to operate while key details remain uncertain.

This article looks at what's known, what's still unconfirmed, and what users should watch next.

What happened to the Drift-linked ETH

A wallet tied to the Drift Protocol hack sent about 25,700 ETH to Tornado Cash over roughly two hours on a Tuesday, following a stretch of around two months with no activity. Lookonchain flagged the transfers in a post on X. At the time of the report, that amount was valued at roughly $61 million.

The bigger question is what's left. Arkham estimated that addresses linked to the exploiter still held about 81,454 ETH, worth around $194 million. Those dollar figures move with ETH's price. The numbers also reflect ETH in identified linked addresses - not necessarily every asset connected to the incident.

The exploit happened on April 1 and was reported to result in losses of about $295 million. Drift is a Solana-based decentralized exchange. In June, the protocol said a forensic investigation by cybersecurity firm Mandiant attributed the attack to UNC6862, a North Korean threat group. That attribution is a useful development, but it still doesn't automatically mean every later transaction can be independently tied to a specific entity beyond linked-address analysis.

DefiLlama ranks the exploit as the third-largest crypto hack of 2026. On that basis, it trails the $387 million Bitget hack and the $320 million Liquid Network exploit. Those rankings rely on how much stolen value is estimated at the time of each incident, so they're more about scale than a precise comparison of how much value might exist today.

What is confirmed, and what is not

From the reporting available so far, the most solid points are the reported Tornado Cash transfer amount, the fact it happened after a period of inactivity, the estimate of ETH remaining in linked addresses, and Drift's stated Mandiant attribution. Several questions remain open:

  • Whether the transferred ETH was withdrawn from Tornado Cash.
  • Whether the funds were swapped into other assets or routed through additional services.
  • Whether any portion of the transferred ETH can realistically be recovered.
  • Whether all addresses identified by analytics firms are controlled by the same actor.

This distinction matters. A transfer is visible on-chain. But control, intent, and eventual recoverability are much harder to prove from transaction history alone. Treating an analytics label like a confirmed identity would go further than the evidence supports.

What a Tornado Cash transfer does - and does not - mean

Tornado Cash is a cryptocurrency mixer. In simple terms, mixers pool deposits and make it harder to connect a specific deposit to a later withdrawal. That can complicate tracing, which normally works by following assets through public transaction histories from address to address.

The real effect is added uncertainty, not a "disappearance." The original deposit is still recorded on the blockchain. Analysts can still look at timing, amounts, wallet behavior, and other on-chain signals. But once funds move through a mixing service, the link between an initial deposit and a later withdrawal can get less direct - especially when many users interact with the same infrastructure.

It's also important to separate a mixer transfer from a confirmed cash-out. The reported movement doesn't prove that the ETH was exchanged for fiat, that it reached a regulated platform, or that the full amount is now permanently out of reach. Those would require separate evidence.

Why the timing draws attention

Returning to activity after about two months of inactivity is notable for investigators and market observers because it changes what we think about those linked wallets. It doesn't, by itself, explain why the transfers happened. The timing could fit with an attempt to move funds, but the available reporting doesn't establish motive.

The transfer is another reminder that major incidents often stay "live" long after the breach. Investigators may keep tracking funds, analytics providers may flag activity, and victims may wait for a recovery process to move forward. An address that was quiet can start moving again, and the value at stake can shift as ETH's market price changes.

For users, the practical takeaway is straightforward: don't treat "sent to Tornado Cash" as shorthand for "gone forever." It suggests tracing may get tougher, not that recovery is impossible. It still leaves open questions about identity, access, any law-enforcement action, and how much recovery may ultimately happen.

How the transfer relates to Drift's recovery process

Drift opened claims and redemptions for DFX recovery tokens on October 1. The tokens are meant to give affected users a claim on a recovery pool. At launch, that pool held about $3.1 million, with expectations that it would receive exchange revenue and any recovered exploit funds.

The gap between the reported $295 million losses and the pool's initial size is large. That doesn't tell you what users will ultimately receive, and it doesn't mean the recovery effort is over. But it does explain why a recovery claim isn't the same as immediate repayment. A token representing a claim on a pool is not the same thing as cash already sitting there to pay everyone in full.

A reported $61 million transfer could matter if funds later prove recoverable - but the transfer itself doesn't automatically add assets to the pool or guarantee changes to payouts. Recovery depends on what can be traced, controlled, and returned, and on how the claims process is structured. The reporting that flagged the transfer doesn't say that any of the moved ETH has been recovered.

What affected users should verify

If you were affected, the safest move is to use Drift's official channels to confirm the current claims process and token terms. In particular, double-check:

  • Eligibility requirements and claim deadlines.
  • How DFX tokens represent a claim and whether they can be transferred.
  • How exchange revenue flows into the recovery pool.
  • How recovered funds, if any, are distributed.
  • Whether any site or message asking you to connect a wallet is actually an official Drift resource.

Don't treat a social post or an unsolicited message as proof that you qualify for extra funds. Recovery events attract impersonation attempts, especially when people are waiting for updates. And never share a seed phrase or private key to claim anything. A legitimate recovery process should not require that.

What users and the DeFi market should watch

For this incident, the most useful next signals are the ones you can verify and observe. Watch for Drift updates about the DFX pool and claims process, credible reporting on whether the ETH left Tornado Cash, and any verified announcements tied to recovery or seizure. A transfer alone isn't enough to conclude funds were recovered, laundered in a way that defeats tracing, or converted into other assets.

There's also a broader point for DeFi teams: security doesn't stop at preventing the initial exploit. Incident response includes preserving evidence, communicating what's known, supporting affected users, and running a recovery process over time. Those steps involve different constraints. Publishing early attribution can help users understand the investigation, but it should stay distinct from confirmed transaction facts. A recovery token can create a structured claim, but its real value depends on transparent rules and on what assets actually reach the pool.

For users evaluating a DeFi protocol, the question isn't just whether it has been hacked before. Risk can't be driven to zero. The more practical questions are how the team responds when controls fail, how quickly it communicates, whether users can verify the recovery mechanism, and whether the protocol explains what any promised reimbursement can and can't cover.

The Drift case also highlights why headline rankings can mislead. A $295 million loss tells you something about scale, but it doesn't tell you what might be recovered, how many people were affected, or how losses were distributed. Those details are usually what matter most when deciding whether a recovery claim is worth pursuing - or how much risk a protocol carries.

The current situation can be stated without speculation:

  • About $61 million in ETH was sent from a wallet linked to the exploit to Tornado Cash.
  • Linked addresses were reported to hold about $194 million in ETH afterward.
  • Drift reported about $295 million in losses from the April 1 incident.
  • Drift opened DFX recovery-token claims and redemptions, with a pool that held about $3.1 million at launch.
  • The reported transfer doesn't establish that the ETH has been cashed out or recovered.

That's what users can act on today. Anything else should be treated as developing until there's verifiable evidence.

Conclusion

The movement of $61 million in ETH is a meaningful new development in the Drift exploit, but it's not the whole story. It makes tracing more complicated and leaves open whether the funds can be followed, recovered, or tied to later activity. Meanwhile, Drift's recovery process is running through DFX tokens and a pool that began with about $3.1 million.

If you're an affected user, verify claim details through Drift's official channels and treat any talk of guaranteed reimbursement with caution. If you're tracking the incident as a DeFi investor, focus on confirmed wallet activity, clear recovery terms, and verified updates - rather than conclusions drawn from a single transfer. For the original report and ongoing developments, read Cointelegraph's coverage.

Frequently Asked Questions

The wallet sent about 25,700 ETH, valued at approximately $61 million at the time of reporting. Lookonchain said the deposits occurred over roughly two hours after about two months of inactivity.
Arkham estimated that linked addresses held about 81,454 ETH, worth roughly $194 million at the time. These are analytics-based estimates, and the dollar value changes with ETH’s market price.
No. A mixer can make it more difficult to connect deposits with later withdrawals, but it does not delete the original blockchain transactions. The transfer also does not prove that the ETH has been withdrawn, exchanged or recovered.
Not by itself. Drift’s DFX recovery pool receives exchange revenue and any recovered funds, but the reported transfer is not evidence that the ETH has been returned or added to the pool. Users should consult Drift’s official updates for current claim terms.

Related articles