The $25M Lesson That Cost Nothing: Why the Same Wallet Got Drained Twice
Hook
Fifteen minutes. That’s all it took for two wallets holding over $25 million in crypto assets to go from full to zero. The attacker didn’t exploit a smart contract bug or a flash loan trick. They didn’t need to. They had the private keys. The victim? The same whale who lost $24 million in a phishing attack back in 2023—and got 90% of it returned. Now, history repeats with a deadlier twist. This isn’t a protocol failure. It’s a user failure. And it’s the most expensive kind. — Root: Auditing the DAO and Ethereum.
Context
On [date], Scam Sniffer flagged a massive drain: two addresses belonging to a single entity were emptied within 15 minutes. The stolen assets included DAI, WBTC, aUSDC, LDO, sUSDe, and ETH—a diversified portfolio spanning Aave, Lido, Ethena, and Maker. The attacker converted everything to DAI and ETH within an hour, then dispersed the funds across multiple addresses. The attack vector: private key leak, not a phishing approval. This is critical. The same victim had been hit in 2023 via a phishing signature that drained 4,851 rETH and 9,579 stETH. That time, the attacker returned ~90% of the funds after community pressure and on-chain tracking. This time, the attacker is moving fast—and profit is the only goal.
The victim’s behavior post-2023 is telling. They didn’t switch to a hardware wallet, didn’t set up multisig, didn’t revoke old approvals. They kept the same wallets, the same habits, and the same exposure. The attacker waited. Then struck when the defenses were still zero.
Core
Private key leaks are the silent killer of crypto. Unlike phishing, which requires user interaction (signing a malicious transaction), a private key leak gives the attacker full, immediate control. No approval needed. No waiting. The attacker can move assets at will, and they do it with automated scripts.
From my experience auditing the DAO and Ethereum in 2016, I learned that the most devastating vulnerabilities are often the simplest. The DAO reentrancy was a code bug, but private key leaks are a human bug. They are harder to fix because the solution is not a patch—it’s behavior change.
Let’s break down the possible leak paths for this victim, based on the evidence:
- Mnemonic stored digitally (high confidence): The victim was a phishing target in 2023, meaning they were already on attackers’ radar. They likely stored their seed phrase in a cloud service, email, or screenshot. Attackers who gained access to their device (via malware or social engineering) could have exfiltrated the keys and waited. The fact that both wallets were drained simultaneously suggests the attacker had access to the same seed source.
- Malware on device (medium confidence): The victim’s history of clicking phishing links makes them a prime target for targeted malware—keyloggers, clipboard hijackers, or remote access trojans. The 15-minute drain speed indicates the attacker had pre-built scripts designed to sweep any whitelisted assets.
- Third-party tool exposure (low confidence): The victim managed a large portfolio. They may have used a portfolio tracker, tax software, or a custom script that exposed the private key. This is less likely given the lack of evidence, but not impossible.
- Social engineering (low confidence): The attacker could have impersonated a support agent or a friend to extract the seed phrase. But given the precision of the attack, it’s more likely a technical compromise.
Why does the speed matter? The attacker converted all assets to DAI and ETH within 60 minutes. This is a standard “de-risking” move: they swapped volatile tokens (WBTC, LDO, sUSDe) for highly liquid, privacy-friendly assets. DAI and ETH are easier to move through mixers (Tornado Cash, Railgun) or cross-chain bridges. The attacker is not holding for speculation—they are cleaning the trail.
The aUSDC signal: The victim held aUSDC, a deposit token for Aave. This means they had an active lending position. If the assets were pulled, any borrowed positions could be liquidated, causing cascading effects. However, the attacker drained the wallet directly, so the Aave position may already be closed or the victim had no debt. Still, this is a secondary risk that DeFi protocols should monitor.
Compare to 2023: That attack was a phishing approval—the victim signed a malicious “increase allowance” transaction. The attacker could only move specific tokens (rETH, stETH) and had to rely on the victim’s approval. The slow speed gave tracking teams time to freeze funds. This time, the attacker had full control. No approvals needed. No time to react. — Root: Auditing the DAO and Ethereum.
The core insight: Private key leaks are the most devastating attack vector because they bypass all on-chain safeguards. No multisig threshold, no timelock, no revoke option can save you if the attacker has the key. The only defense is prevention: never expose the key.
Contrarian
The market’s knee-jerk reaction to this story is “self-custody is too risky, use a centralized exchange.” That’s the wrong lesson. The real problem is not self-custody vs. custody—it’s the lack of a security mindset. The victim used self-custody carelessly. They didn’t lose because they held their own keys; they lost because they held them badly.
Furthermore, the 2023 refund created a dangerous false sense of security. The victim (and many others) internalized that “even if I get hacked, I might get my money back.” That expectation is irrational. The 2023 attacker returned funds due to pressure from the community and on-chain surveillance—a rare outcome. This time, the attacker is using a different method, likely a different group, and has no incentive to return. The market should not expect a repeat.
Another contrarian angle: The crypto industry’s obsession with “liquidity fragmentation” as a problem is a distraction. The real fragmentation is in security responsibility. Protocols build flashy products but offload all security risk to users. The industry needs to move to default security: account abstraction (ERC-4337), social recovery, hardware wallet integration, and mandatory approval limits. Until then, stories like this will keep happening.
Takeaway
If you hold more than $100k in crypto, you have a target on your back. The victim’s story is a warning, not a one-off. Private key leaks are the new normal, and they will keep hitting the same people because the industry’s security education is abysmal.
Actionable steps: - Use a hardware wallet (Ledger, Trezor) for any amount over $10k. - Never store seed phrases digitally. Write them on steel plates. - Use a multisig wallet (Safe) for teams or large holdings. - Revoke old approvals regularly (revoke.cash). - Assume you are compromised until proven otherwise.
The question is not “will you be hacked?” but “when will you be hacked?” — and whether you have prepared for it. This victim didn’t. They lost $25M, twice. The lesson cost them everything. It can cost you nothing if you learn it now.
We farmed the yields until the protocol farmed us. — Root: Auditing the DAO and Ethereum.