Drift Exploit: $61.56M in ETH Sent to Tornado Cash12 min read2,474 words

Drift Exploit: $61.56M in ETH Sent to Tornado Cash

Wallets linked to the Drift exploit sent 25,700 ETH to Tornado Cash. Learn what the $61.56M transfer means, what funds remain, and how recovery works for users.

Drift exploitTornado CashEthereum transfersDeFi recoveryDrift Protocol
Drift Exploit: $61.56M in ETH Sent to Tornado Cash

$61.56 Million in ETH Moves From Drift Exploit Wallets to Tornado Cash

Wallets linked to the $295 million Drift Protocol exploit have sent another 25,700 ETH - about $61.56 million at the time of the transfers - to Tornado Cash. Deposits came in batches over roughly two hours, after the addresses reportedly sat quiet for around two months.

This kind of movement is noteworthy, but it doesn't mean the funds are gone or that the attacker has successfully cashed out. Transfers are still visible on-chain, and mixers mainly make it harder to connect deposits to withdrawals. The latest activity also follows an earlier round of deposits in July, with a large balance still reportedly sitting in wallets attributed to the exploiter.

For Drift users, these transfers are only one thread in a longer story: the April 1 exploit, the investigation into who was responsible, and a recovery plan whose initial funding pool was much smaller than the verified losses. Below is what the on-chain data supports, what it doesn't prove, and how Drift's recovery mechanism is meant to work.

What happened to the Drift exploit funds

Wallets tied to the April 1 Drift Protocol attack deposited 25,700 ETH into Tornado Cash over about two hours on Tuesday, according to reporting and blockchain data cited by Decrypt. The ETH was valued at roughly $61.56 million when the transfers happened. The deposits reportedly included batches around 100 ETH, along with smaller 10 ETH transactions.

The transfer sizes matter because they match fixed deposit pool amounts used by the mixer. Even so, deposit size alone can't tell you who initiated each transfer or what happened to the funds afterward. The addresses are described as linked to the exploiter based on tracking and attribution - not the same thing as an actual court finding about a specific person.

The latest deposits are not the first

This was the second reported round of deposits. On July 23 and 24, an address labeled "Drift Exploiter 4" sent about 23,095 ETH to Tornado Cash, worth roughly $44.4 million at the time. Taken together, the two reported rounds total about 48,795 ETH sent to the mixer.

That number shouldn't be treated as the attacker's whole balance, and it doesn't prove that all of those funds were later moved out into new wallets. Those are different questions: deposits are one step, while withdrawals, current control, and any recovered funds are separate outcomes.

A large balance remains in tracked wallets

Arkham Intelligence's entity view reportedly tracks 71 addresses associated with the exploiter. After the latest deposits, those tracked wallets still held 81,454 ETH, valued at about $198.58 million at the time of the report. The same portfolio view also showed around $561,600 in other assets, including USDT, USDC, Solana, and USDY.

These figures are snapshots. Token prices change, assets can be moved, and wallet labels depend on the attribution evidence available at the time. Still, the overall picture is clear: the Tornado Cash deposits are sizable, but they're only part of what's been attributed to the exploit in the tracked portfolio.

Arkham's portfolio view also showed one Fartcoin worth roughly 15 cents. It's a small detail, but it points to a practical limitation of portfolio snapshots: token balances can remain in an address even if they're not directly connected to the main activity. Drift has said about $4.1 million in Fartcoin was taken in the attack - quite different from the token balance shown in the tracked wallets.

What Tornado Cash transfers do - and do not - tell us

Tornado Cash is a crypto mixer. In simple terms, a user deposits cryptocurrency into a pool and can later withdraw it through a different address. Fixed deposit amounts can make it harder for observers to link a specific deposit to a specific withdrawal, which may explain why the reported transfers used round numbers like 100 ETH and 10 ETH.

A mixer doesn't erase the deposit transaction from the blockchain. The transaction record, amount, and destination contract remain there. What the service changes is how difficult it is to connect withdrawals to particular deposits - not whether the activity is visible at all. Analysts can still look at timing, amounts, and other on-chain signals, and investigators may also combine on-chain data with information from outside the chain.

A deposit is not proof of a successful cash-out

The reported transactions show ETH going to Tornado Cash from addresses attributed to the exploiter. They don't, by themselves, prove that the ETH was later withdrawn, converted to fiat, or spent. You'd need evidence of additional activity to support that.

This matters because "sent to a mixer" often gets used as shorthand for "laundered." Public data can support "deposited into a mixer," but it can't automatically support "fully cashed out" at the same moment in time. A mixer deposit may be an attempt to complicate tracing, but it's not the same thing as demonstrating the assets have disappeared from scrutiny entirely.

For people tracking the incident, it helps to keep three questions separate:

  • What is visible? The deposit transactions and their amounts.
  • What is attributed? The assessment that the sending addresses connect to the Drift exploiter.
  • What remains unknown? Whether, when, and how the funds were withdrawn or converted after the deposits.

Keeping those categories distinct gives a cleaner picture than treating every wallet movement as the end of the story.

The value is a snapshot, not a fixed loss estimate

The $61.56 million figure is an estimate of the value of 25,700 ETH at the time of the reported transfers. That number will move with Ethereum's price. It also shouldn't be added to the original exploit total as if it were a new loss. The transfer is a movement of assets already tied to the attack, not a separate new incident against Drift.

The same caution applies to wallet-tracking services. Dollar values are helpful for scale, but they can change quickly. The ETH amounts are the steadier measure of what moved; the USD figure is just an approximate market value at one point in time.

The Drift exploit and the recovery plan

The Drift attack happened on April 1 and affected vaults on Solana. Drift's breakdown puts the haul at about $295.7 million. The biggest reported components were roughly $159.3 million in JLP (the Jupiter Liquidity Provider token) and $71.4 million in USDC. Much of that value was later swapped and bridged to Ethereum, which helps explain why a lot of the later wallet tracking shows ETH.

Drift has said the attacker gained administrative powers, introduced a fake token, and used it to borrow real liquidity. In April, the protocol described the operation as a six-month effort: posing as a quantitative trading firm, meeting contributors in person, and depositing $1 million of its own money to build trust. In June, Drift said forensic firm Mandiant attributed the attack to UNC6862, a North Korean threat group. That's Drift's account of the attribution - the wallet transfers themselves don't independently identify the people behind the attack.

DFX claims are not equivalent to immediate repayment

Drift - whose relaunched exchange operates as Velocity - opened claims for its DFX recovery token on October 1. Reporting says the plan issued one token for each USDT of verified loss, for about 299.5 million tokens in total.

At launch, the recovery pool held about 3.1 million USDT. If that pool were spread evenly across all 299.5 million tokens, it would work out to roughly 0.0104 USDT per token - about one cent per dollar of verified loss. In other words, a claim represented as one token per dollar doesn't mean each token can immediately be redeemed for $1.

That distinction is key to understanding the recovery plan. DFX tokens represent a claim within the system; what holders can redeem depends on what the pool actually holds and how distributions are structured. Since the initial pool was only a small fraction of the verified losses, early claimants shouldn't assume the token's face value equals cash already available for repayment.

Revenue and recovered assets are intended to build the pool

The recovery pool is set up to receive a daily share of Velocity's net protocol revenue - reported as between 60% and 90%, with the percentage increasing as daily revenue rises. Tether has also committed up to 127.5 million USDT toward the relaunch and recovery. "Up to" matters here: it sets a ceiling for the commitment, not proof that the full amount was already in the pool when claims started.

Drift has also said funds recovered through freezes, bounties, or law enforcement would be added to the pool. Different sources can come with different terms and timelines. Protocol revenue depends on the exchange generating revenue, a commitment could depend on how terms are fulfilled, and stolen-asset recovery can take a long time without any guaranteed result.

For affected users, the practical question isn't only how many DFX tokens were issued. It's how much value ends up in the pool, how distributions are calculated, and how the rules change as revenue and recoveries arrive. Those mechanics determine how quickly repayment can realistically happen.

What the transfers mean for users and the market

The latest deposits are another reminder that responding to an exploit doesn't end when a protocol patches a vulnerability or posts an incident report. Funds can move across chains, through multiple wallets, and into services meant to complicate tracing. For the protocol, investigators, and users, it keeps the operational pressure going - especially when clarity about what's been recovered is still evolving.

At the same time, a single high-value transfer isn't automatically the same kind of market event as the original exploit. This ETH movement matters mainly because it ties back to the incident and may affect prospects for tracing and recovery. It doesn't, by itself, show that the attacker sold 25,700 ETH on the open market. A mixer deposit is not the same thing as a sale, and the fact that substantial ETH remained in tracked wallets afterward suggests this wasn't a complete cash-out.

What affected users should monitor

If you're following the case, it helps to watch multiple signals instead of treating one headline as the whole story:

  • Verified wallet movements: Track the transaction-level updates, and separate transfers from sales or withdrawals.
  • Attribution updates: See whether claims about specific wallets or actors come from Drift, an analytics provider, investigators, or a legal authority.
  • Recovery-pool balances: What's actually available for distribution matters more than the total number of claim tokens issued.
  • Redemption rules: Check eligibility, timing, and any conditions before treating a token balance as recoverable cash.
  • Protocol revenue and asset recovery: These are possible funding sources, but their amounts and timelines aren't fixed.

This isn't just a checklist for convenience. It keeps different kinds of information from collapsing into one number. The exploit's original loss, balances shown in tracked wallets, the amounts sent to Tornado Cash, and the amount in the recovery pool all describe different things.

The broader DeFi lesson is operational, not just technical

Drift's account of a months-long effort - impersonation, in-person meetings, and trust-building - points to a familiar weakness in DeFi security: the risk isn't limited to code bugs. Administrative access, contributor verification, operational procedures, and escalation paths can all become part of the attack surface.

That said, it doesn't automatically follow that every protocol should respond by adding layers of process without weighing the cost. Controls can slow down legitimate work, and poorly designed safeguards can create their own failure modes. The goal is to make high-impact actions harder to abuse: limit privileged access, require independent checks for sensitive changes, define clear emergency procedures, and test how teams respond when an apparent partner behaves suspiciously.

For users evaluating a protocol, technical audits are only one input - they're not a complete guarantee. It's also fair to ask how the project handles administrative permissions, incident communication, asset recovery, and user claims. Controls can't remove risk entirely, but they can affect how bad a failure can get - and how clearly the project responds afterward.

Conclusion

The 25,700 ETH deposit is a major movement of funds tied to the Drift exploit, but it doesn't prove the assets were cashed out or made untraceable. The reported wallet data still showed a substantial ETH balance, and Drift's recovery effort began with a pool far smaller than the verified losses - intended to grow through revenue, commitments, and any recovered assets.

For users, the clearest approach is to keep the numbers separate: funds moved, funds still tracked, funds actually recovered, and funds available for redemption aren't the same thing. Follow updates from Drift and reliable transaction data, and check the recovery terms before assuming what a claim token is worth. Read the source report from Decrypt for the reported transfer details.

Frequently Asked Questions

Wallets linked to the Drift exploiter deposited 25,700 ETH, worth about $61.56 million at the time of the reported transactions. The deposits took place over roughly two hours and followed an earlier reported round of about 23,095 ETH in July.
No. The deposit transactions remain visible on the blockchain. A mixer is designed to make it harder to link a withdrawal to a specific deposit, but the transfer does not erase transaction history or prove that funds have been successfully withdrawn and cashed out.
Arkham’s tracked entity reportedly showed 81,454 ETH across 71 addresses after the latest deposits, worth roughly $198.58 million at the time. Wallet labels and dollar values are estimates that may change as attribution evidence and market prices change.
Not automatically. Drift reportedly issued one DFX token per USDT of verified loss, but the initial recovery pool held about 3.1 million USDT against approximately 299.5 million tokens. Actual redemption depends on pool assets, revenue contributions, recoveries and the program’s distribution rules.
Drift said forensic firm Mandiant attributed the attack to UNC6862, a North Korean threat group. That attribution is reported by Drift; the public wallet movements alone do not establish the identity of the attackers.

Related articles