Yearn Finance Hack Explained: How a 16-Wei Deposit Became $9 Million — and What DeFi Users Must Learn in 2026

Deposits of 16 wei — an amount so small it rounds to zero dollars — should never be able to drain a $9 million liquidity pool. Yet that is exactly what happened at Yearn Finance, one of DeFi's most respected protocols, when its yETH pool was exploited in a single transaction. And now, a new technical analysis from Check Point Research has revealed precisely how the attacker pulled it off — a masterclass in smart-contract accounting failure that every crypto investor should understand.

If you use DeFi, stake Ethereum, or hold tokens in any liquidity pool, this story is a warning. The exploit did not involve phishing, stolen passwords, or compromised wallets. It was a pure logic flaw: a desynchronization between a pool's real balance and its cached "memory" of that balance. Below, we break down what happened, how the attacker turned dust into millions, where the money went, and — most importantly — how you can protect your own crypto from the next DeFi exploit.

What Is Yearn Finance and What Was the yETH Pool?

Yearn Finance is a decentralized finance (DeFi) aggregator on Ethereum, launched in 2020. It automates yield generation: users deposit assets into "vaults," and the protocol routes those assets across lending and liquidity strategies — on platforms like Aave and Compound — to maximize returns. In exchange, depositors receive yield-bearing "yTokens" representing their share of the pool. Yearn's V2 and V3 vault standards are widely respected and heavily audited.

The target of this attack, however, was not a standard Yearn vault. The yETH pool was a custom-built product: a weighted stableswap automated market maker designed to aggregate Liquid Staking Tokens (LSTs) — tokens like wstETH, rETH, apxETH and sfrxETH that represent staked Ethereum. If you are new to these concepts, our guide on what DeFi is and how it works explains the basics, and our Ethereum staking guide covers how liquid staking tokens generate yield.

The yETH pool was a legacy, specialized product sitting alongside Yearn's core vaults. That distinction turned out to be critical: the vulnerability lived in this custom stableswap logic, not in the audited vault code that secures the bulk of Yearn's more than $600 million in total value locked.

How the Yearn Finance Hack Worked — Step by Step

According to Verichains' technical breakdown and the new Check Point Research analysis, the attacker executed the exploit in a single transaction around 21:11 UTC on November 30, 2025. It was one of DeFi's most capital-efficient attacks ever. Here is how it unfolded:

Phase 1: Poisoning the pool's memory

To save gas costs, the yETH pool stored "virtual balances" — cached values called packed_vbs[] — instead of reading live balances on every operation. The attacker exploited a critical oversight: when all liquidity was removed from the pool, the main supply counter reset to zero, but the cached virtual balances did not. The pool's memory and its reality desynchronized. The protocol believed the pool was empty even though phantom balances lingered in storage.

The attacker then cycled deposit-and-withdrawal transactions through flash loans. Each pass left behind tiny residual virtual balances that accumulated over time, quietly inflating the pool's cached view of itself.

Phase 2: Breaking the math

With the cached values corrupted, the attacker submitted highly imbalanced liquidity deposits — extreme inputs that forced the pool's custom stableswap invariant into unstable territory. The pool's fixed-point solver (a Newton–Raphson implementation) could not handle the distorted values and began producing incorrect supply outputs. A separate analysis by QuillAudits describes how the broken invariant triggered an arithmetic underflow — the mathematical equivalent of an odometer rolling backward — letting the attacker mint far more LP tokens than deposited.

Phase 3: The 16-wei deposit

Finally, after completely emptying the pool, the attacker deposited just 16 wei — worth roughly $0.000000000000000045 — spread across the pool's eight supported tokens. Because the cached values were inflated, the protocol interpreted this dust deposit as a first-time deposit and minted tokens based on the phantom balances instead of the negligible input. The result: approximately 235 septillion yETH tokens minted from nothing.

Phase 4: Draining the liquidity

Armed with the over-minted yETH, the attacker called repeated remove_liquidity(0) operations and single-asset withdrawals, draining real assets — ETH and liquid staking tokens like wstETH and rETH — from the pool and from connected Balancer pools. The helper contracts used in the attack had been deployed just minutes earlier and self-destructed afterward to obscure the trail.

The entire sequence — from first manipulation to final drain — happened inside one transaction. Blockchain analysts at PeckShield were the first to flag it publicly, and Nansen's alert system later confirmed an infinite-mint vulnerability in the yETH token contract, not in Yearn's vault infrastructure.

The Money Trail: $9 Million, Tornado Cash and Self-Destructing Contracts

The final tally: roughly $9 million drained. About $8 million came from the main yETH stableswap pool, and another $0.9 million from the yETH–WETH pool on Curve. The pool held approximately $11 million before the attack, meaning the exploiter nearly emptied it.

The attacker converted the fake yETH into a mix of real ETH and liquid staking tokens, then began laundering the proceeds. Roughly 1,000 ETH — worth about $3 million at the time — was routed through Tornado Cash, the sanctioned crypto mixer, to obscure the trail. The remaining funds, around $6 million in various staked Ethereum assets, sat in the attacker's wallet (0xa80d…c822) as of the latest blockchain scans.

There was a partial recovery: Yearn and ecosystem partners coordinated to recover 857.49 pxETH (worth roughly $2.33 million at the time), though the rest disappeared into Tornado Cash, as initial coverage of the incident documented.

In a twist that surprised many observers, Yearn's YFI governance token briefly spiked after the exploit was flagged — climbing from near $4,080 to over $4,160 within an hour. Analysts attributed the move to short-covering and thin liquidity rather than any fundamental confidence, a reminder that token prices in a panic often reflect positioning, not reality.

Yearn's Response: What Was Safe and What Wasn't

Yearn Finance confirmed the incident on X, stating: "We are investigating an incident involving the yETH LST stableswap pool. Yearn Vaults (both V2 and V3) are not affected." The protocol later clarified that:

• Yearn's V2 and V3 vaults — where the vast majority of user funds sit — were completely unaffected.
• The yUSND pool and Nerite's vaults remained secure and were not impacted.
• Deposits into the affected pool were isolated while the team and external security experts investigated.
• Impacted users were advised to open a support ticket on the project's Discord channel.

Yearn said it is working with outside security teams on a full post-mortem and patch. The incident drew uncomfortable parallels to Yearn's earlier yDAI vault exploit, which drained $11 million — proof that even battle-tested protocols carry risk in their custom, unaudited edges. For a broader picture of how often this happens across the industry, see our report on crypto hacks hitting $1.18 billion in a single quarter.

Why This Hack Matters for Ethereum and DeFi Security

The Yearn exploit is not just another DeFi hack story. It exposes three structural risks that apply to every protocol you interact with:

1. Gas optimization can create security holes. The packed_vbs[] caching existed to save users gas fees — a noble goal. But every shortcut in accounting logic is a potential attack surface. The desync between cached and real balances is the kind of subtle flaw that standard audits can miss, especially in custom code.

2. "First deposit" logic is a classic attack vector. Many AMMs have special handling for the first liquidity deposit, when no price reference exists. Attackers repeatedly target this edge case — donating or manipulating balances to inflate the first-deposit calculation. If a protocol you use has custom pool logic, this is the line of code you want audited.

3. Legacy products are the weak link. Yearn's core vaults survived because they are standardized and heavily reviewed. The yETH pool was a legacy side product with custom logic. In DeFi, always ask: is my money in the protocol's flagship product, or in an experimental side pool with less scrutiny?

As Check Point Research's new findings underline, the attack required no insider access and no user error — just a deep understanding of the pool's accounting. That is what makes smart-contract risk fundamentally different from exchange risk, and why DeFi users need a different security playbook.

How to Protect Your Crypto From DeFi Exploits

You cannot audit smart contracts yourself — but you can dramatically reduce your exposure. Here is a practical checklist drawn from this incident and years of DeFi post-mortems:

• Prefer flagship products over legacy side pools. Put funds in a protocol's core, battle-tested vaults rather than custom one-off products. The yETH pool was a side product; Yearn's V2/V3 vaults were untouched.
• Check how long the code has been live and audited. Newly deployed or unaudited contracts — like the attacker's self-destructing helper contracts — are red flags. Look for multiple independent audits and a public bug-bounty program.
• Diversify across protocols. Never keep your entire stack in one pool or one protocol. A single exploit should never be a portfolio-ending event.
• Watch total value locked (TVL). The yETH pool held only ~$11 million — thin liquidity makes manipulation cheaper. Deep, long-standing pools are harder to attack.
• Use a hardware wallet for anything you hold long-term. Self-custody in a hardware wallet keeps your assets out of smart-contract risk entirely. Our comparison of the best crypto wallets for beginners explains hot vs. cold storage.
• Revoke unused token approvals regularly. Old approvals to contracts you no longer use are a standing invitation. Review and revoke them with a tool like Revoke.cash.
• Treat unaudited yield as a risk premium, not free money. If a pool offers yields far above the market, the extra return is compensation for extra risk — price it accordingly.

For a complete step-by-step security setup, read our full guide: How to Protect Your Crypto From Hacks and Scams in 2026.

Frequently Asked Questions

What happened in the Yearn Finance hack?

On November 30, 2025, an attacker exploited an accounting flaw in Yearn Finance's yETH weighted stableswap pool on Ethereum, minting approximately 235 septillion yETH tokens from a 16-wei deposit and draining roughly $9 million in ETH and liquid staking tokens — all in a single transaction.

Was Yearn Finance's main product affected?

No. Yearn confirmed that its V2 and V3 vaults — where the majority of user funds are held — were completely unaffected. The vulnerability was isolated to the legacy yETH stableswap pool, a custom side product. The yUSND pool and Nerite's vaults were also unaffected.

How did 16 wei become $9 million?

The pool cached "virtual balances" to save gas. When the pool was emptied, the real supply counter reset to zero but the cached balances did not. The attacker inflated these cached values through flash-loan deposit/withdrawal cycles, then made a tiny 16-wei deposit that the protocol treated as a first-time deposit — minting yETH based on the inflated phantom balances instead of the real input.

Where did the stolen funds go?

The attacker converted the minted yETH into real ETH and liquid staking tokens. About 1,000 ETH (~$3 million) was laundered through Tornado Cash. Roughly $6 million in staked ETH assets remained in the attacker's wallet, while Yearn and partners recovered about 857.49 pxETH (~$2.33 million).

Is Yearn Finance safe to use now?

Yearn's core V2/V3 vaults were never compromised and remain among DeFi's most audited products. However, the incident is a reminder to use flagship, audited products, diversify across protocols, and keep long-term holdings in self-custody. No DeFi protocol is risk-free.

What is the new Check Point Research report about?

Check Point Research published a new technical analysis in October 2026 detailing the exploit's mechanics — the cached-storage desync, the flash-loan balance poisoning, and the 16-wei first-deposit trick. The findings, reported by Infosecurity Magazine, serve as a case study in how gas-optimization shortcuts can become critical vulnerabilities.

Conclusion

The Yearn Finance yETH exploit is the purest kind of DeFi cautionary tale: no phishing, no stolen keys, no insider — just a subtle desynchronization between what a smart contract remembered and what was true. A 16-wei deposit, worth effectively nothing, became $9 million because cached virtual balances were trusted over real ones.

The new Check Point Research analysis gives the industry a precise autopsy to learn from: audit custom accounting logic ruthlessly, distrust gas-optimization shortcuts, and treat "first deposit" edge cases as the attack surface they are. For users, the lesson is simpler — stick to flagship audited products, diversify, revoke old approvals, and keep your long-term stack in cold storage.

DeFi's promise is permissionless yield. Its price is eternal vigilance. The 16-wei hack proves that in smart-contract security, the smallest numbers can cause the biggest damage.