Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

The $9M yETH Exploit: How 16 Wei Became Infinite Tokens

0
Critical
Exploit
Published: Tue Dec 02 2025 (12/02/2025, 13:42:36 UTC)
Source: Check Point Research

Description

By: Dikla Barda, Roman Zaikin, and Oded Vanunu On November 30, 2025, Check Point Research detected a critical exploit targeting Yearn Finance’s yETH pool on Ethereum. Within hours, approximately $9 million was stolen from the protocol. The attacker achieved this by minting an astronomical number of tokens—235 septillion yETH (a 41-digit number)—while depositing only 16 […] The post The $9M yETH Exploit: How 16 Wei Became Infinite Tokens appeared first on Check Point Research .

AI-Powered Analysis

AILast updated: 12/02/2025, 13:43:37 UTC

Technical Analysis

The $9M yETH exploit on November 30, 2025, targeted Yearn Finance's yETH pool, a liquid staking token representing a basket of Ethereum-based liquid staking derivatives (LSDs). The core vulnerability was a cached storage flaw in the pool's management of virtual balances (packed_vbs[]), which are used to optimize gas costs by storing pre-calculated virtual balances representing the value of assets in the pool. When the pool was fully drained, the main supply counter reset to zero, but the cached virtual balances were not cleared, leaving residual phantom values. The attacker exploited this by performing multiple deposit-withdraw cycles using flash loans to poison the packed_vbs[] storage with small residuals. After withdrawing all liquidity, the pool's supply was zero but packed_vbs[] contained accumulated phantom balances. When the attacker deposited a minuscule amount (16 wei), the protocol triggered its “first-ever deposit” logic, reading stale cached values and minting an astronomical number of yETH tokens (235 septillion). The attacker then swapped these tokens for underlying assets and converted them to ETH, repaid flash loans, and laundered funds via Tornado Cash. The vulnerability stemmed from incomplete state cleanup in remove_liquidity() and add_liquidity() functions, where the edge case of full liquidity removal was not handled properly. This exploit demonstrates the risks of complex DeFi protocols using advanced AMM invariants and gas optimization techniques without rigorous state management and testing. Prevention requires explicit resetting of cached states upon full withdrawal, transaction sequence simulation to detect abnormal minting ratios, and runtime monitoring to block suspicious liquidity additions. This incident underscores the need for evolving on-chain security from reactive forensics to proactive, logic-aware defenses.

Potential Impact

The exploit resulted in the theft of approximately $9 million from Yearn Finance's yETH pool, undermining trust in the protocol and potentially destabilizing the broader DeFi ecosystem relying on liquid staking derivatives. For European organizations and users engaged in DeFi, especially those interacting with Yearn Finance or similar Ethereum-based protocols, the impact includes direct financial loss, erosion of confidence in DeFi platforms, and increased regulatory scrutiny. The exploit also highlights systemic risks in DeFi protocols that use cached state optimizations without comprehensive edge case handling, which could lead to similar attacks on other protocols. European crypto funds, institutional investors, and retail users exposed to yETH or related tokens may suffer asset devaluation or theft. Additionally, the laundering of stolen funds through mixers like Tornado Cash complicates attribution and recovery efforts, potentially affecting compliance and anti-money laundering (AML) frameworks in Europe. The incident may prompt European regulators to enforce stricter security standards and transparency requirements for DeFi platforms, impacting operational costs and innovation pace. Overall, the exploit threatens financial integrity, user trust, and regulatory compliance within the European DeFi market.

Mitigation Recommendations

1. Explicitly reset cached virtual balances (packed_vbs[]) to zero whenever the pool’s total supply reaches zero to prevent residual phantom balances. 2. Implement comprehensive unit and integration tests covering edge cases, especially full liquidity withdrawal scenarios, to ensure state consistency. 3. Deploy real-time transaction simulation tools that analyze minting ratios and detect abnormal token issuance patterns before execution, blocking suspicious transactions. 4. Monitor multi-transaction sequences to identify state poisoning attempts involving repeated deposit-withdraw cycles, which single-transaction monitoring may miss. 5. Integrate runtime protocol logic-aware defenses that understand the mathematical invariants and expected state transitions to detect and prevent exploits proactively. 6. Conduct regular third-party security audits focusing on gas optimization techniques and cached state management. 7. Encourage transparency and rapid disclosure of vulnerabilities and exploits to enable coordinated incident response. 8. For European DeFi platforms, enhance AML and KYC procedures to detect and prevent laundering of stolen assets through mixers and decentralized exchanges. 9. Educate developers on the risks of caching state in complex DeFi protocols and promote best practices for explicit state management. 10. Collaborate with blockchain security firms to deploy advanced anomaly detection systems tailored for DeFi protocols.

Need more detailed analysis?Get Pro

Technical Details

Article Source
{"url":"https://research.checkpoint.com/2025/16-wei/","fetched":true,"fetchedAt":"2025-12-02T13:43:16.999Z","wordCount":1459}

Threat ID: 692eecf55ae7112264d1dd7a

Added to database: 12/2/2025, 1:43:17 PM

Last enriched: 12/2/2025, 1:43:37 PM

Last updated: 12/4/2025, 11:50:05 AM

Views: 25

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats