
KelpDAO Exploit Fallout: Ethereum Lost $38.4 Billion in Liquidity
Seven months after the attack, the numbers still tell a stark story about what a single exploit can do to an entire ecosystem. The KelpDAO exploit happened on April 18, 2026, and the initial exploit drained roughly $292 million, but the damage did not stop there. Between April and November 2026, Ethereum’s stablecoin and tokenized-fund market cap fell from $206.7 billion to $168.3 billion, a drop of 19 percent that represents a $38.4 billion contraction in liquidity. That is the finding of a retrospective analysis published on November 10, 2026, and it reframes the KelpDAO incident from a single protocol’s bad day into one of the most consequential events in decentralised finance this year. This retrospective looks back at how it worked, why it spread so far beyond its original target, and the lesson it leaves behind.
April 18, 2026: how the attack unfolded
The KelpDAO exploit began with infrastructure rather than with a flaw in a smart contract’s logic. Attackers compromised internal RPC nodes, the servers that decentralised applications use to communicate with the blockchain, and executed a distributed denial-of-service attack, a flood of traffic designed to overwhelm systems and disrupt their normal operation. The combination was deliberate. By compromising the nodes and flooding the network at the same time, the attackers created the conditions in which a deeper vulnerability could be exploited, and they understood the system they were attacking well enough to know which piece would give way first. The initial exploit drained roughly $292 million, a figure large enough on its own to rank among the most serious incidents of the year. But the size of the initial theft, while shocking, is not the most important part of the story. What matters more is the mechanism that followed, because it shows how an attack on one part of the infrastructure can be converted into a far larger extraction through the interconnected machinery of DeFi. The attackers did not simply steal funds and leave. They used the forged assets they created to borrow real ether from one of the largest lending protocols in the ecosystem, and that second step is what turned a large theft into a systemic event.
The LayerZero DVN flaw: a 1-of-1 setup
At the heart of the attack was a configuration weakness in the way messages were verified between chains. The attackers forced a LayerZero Decentralized Verifier Network, known as a DVN, that had been configured in a vulnerable 1-of-1 setup to accept forged state data. A verifier network exists to check that information arriving from another chain is genuine before it is acted upon, and the number in its configuration describes how many independent verifiers must agree before a message is accepted. A 1-of-1 setup means that a single verifier is enough, so there is no second opinion, no cross-check, and no redundancy if that one verifier is compromised or misled. It is the weakest possible arrangement for a component whose entire purpose is to provide trust, and the attackers understood that. Once the DVN accepted the forged state data, the path was open for the attackers to mint 116,500 unbacked rsETH, tokens that claimed to represent staked ether but were backed by nothing at all. The figure is precise and damning. More than one hundred thousand tokens, each purporting to be a legitimate receipt for ether locked in staking, were created out of thin air because a single verifier, operating alone, said that the data supporting them was real.
Forged rsETH and the Aave borrow
The forged rsETH was not an end in itself. It was a tool, and the attackers used it exactly as a tool is meant to be used. They deposited the forged assets into Aave as collateral, presenting them to the lending protocol as if they were genuine staked ether, and borrowed real ether against them before oracles updated. Oracles are the services that supply price information to DeFi protocols, and they are the mechanism by which a protocol like Aave knows what the collateral deposited with it is actually worth. The attack depended on timing. The forged tokens were accepted as collateral in the window before the oracles caught up with reality, and in that window the attackers were able to extract real ether, an asset with genuine value, in exchange for tokens that had none. This is the step that separates a sophisticated attack from a simple theft. The attackers did not need to break Aave’s smart contracts. They needed to present Aave with something that looked valuable at the moment it was checked, and the combination of a compromised verifier and a slow oracle gave them exactly that opening. The borrowed ether was real, the collateral was not, and by the time the discrepancy became visible, the value had already moved.
Aave’s TVL plunges and the USDT pool runs dry
The consequences for Aave were immediate and severe. Aave’s total value locked, the standard measure of how much capital is deposited in a protocol, plunged 33 percent within 72 hours of the attack. A fall of one third in three days is not a gradual loss of confidence. It is a run, in which depositors and users withdraw their funds as quickly as they can once they understand that something has gone wrong. The speed of the fall shows how quickly trust can evaporate in DeFi, where deposits can be moved in minutes and where the news of an exploit travels through the ecosystem almost instantly. The damage was not limited to Aave’s headline figure. USDT pool availability dropped to a critical $2,540, a number that is almost absurdly small for a pool that should hold vastly more of the world’s most widely used stablecoin. A pool with only $2,540 available is effectively empty, and it means that users who wanted to withdraw their USDT could not do so.
Ethereum loses $38.4 billion in liquidity
The most striking finding of the November 10 retrospective is the scale of what happened to Ethereum as a whole. Ethereum’s stablecoin and tokenized-fund market cap fell from $206.7 billion to $168.3 billion between April and November 2026, a 19 percent drop that amounts to a $38.4 billion contraction. Stablecoins and tokenized funds are the lifeblood of DeFi, because they are the assets that users hold, trade, lend and borrow, and a contraction of this size means that a substantial share of the capital that once sat on Ethereum is no longer there. It is important to be precise about what the figure shows. It does not mean that $38.4 billion was stolen. The initial exploit drained roughly $292 million, a large sum but a small fraction of the total contraction. The rest of the $38.4 billion represents capital that left Ethereum after the attack, either because its owners withdrew it in response to the incident or because they chose to move it somewhere they considered safer. The $38.4 billion figure is therefore best read as a measure of the ecosystem’s reaction to the attack, and that reaction was severe. Some of the capital rotated toward alternative networks: Tron recorded a positive 24.07 percent change in total value locked over 30 days, while Aave’s total value locked remains heavily depressed.
The lesson: infrastructure is the other half of security
The KelpDAO episode leaves a lesson that the DeFi industry cannot afford to ignore. Smart-contract security is only half the battle. The contracts themselves, the code that defines how a protocol behaves, have received enormous attention from auditors, researchers and developers, and that attention is justified. But the infrastructure around those contracts, the RPC nodes that connect applications to the chain, the verifier networks that check cross-chain messages, and the oracles that supply price data, is equally capable of failing, and when it fails, the consequences can be just as severe. The attack succeeded because an RPC compromise and a denial-of-service flood created an opening, because a DVN configured 1-of-1 accepted forged data without a second check, and because an oracle lag allowed forged collateral to be borrowed against before the truth caught up. No single one of those failures would necessarily have been enough on its own. Together, they formed a chain in which each weak link amplified the next.
Frequently asked questions
What happened in the KelpDAO exploit?
On April 18, 2026, attackers compromised internal RPC nodes and executed a DDoS attack, forcing a LayerZero DVN in a vulnerable 1-of-1 setup to accept forged state data. They minted 116,500 unbacked rsETH and deposited it into Aave as collateral to borrow real ETH before oracles updated. The initial exploit drained roughly $292 million.
How much liquidity did Ethereum lose?
Ethereum’s stablecoin and tokenized-fund market cap fell from $206.7 billion to $168.3 billion between April and November 2026, a 19 percent drop and a $38.4 billion contraction, according to the retrospective analysis published November 10, 2026.
What happened to Aave?
Aave’s TVL plunged 33 percent within 72 hours of the attack, and USDT pool availability dropped to a critical $2,540. Aave’s TVL remains heavily depressed months later, showing the damage was not a brief shock.
Source: Binance Square
—
—
Related reading on MM Crypto Analysis Web
- Aave and Morpho Take Competing DeFi Lending Frameworks to the SEC
- Aave DAO Approves Native Bitcoin as Collateral in Aave V4 via Babylon Vaults
- Coinbase Adds DeFi Tokens SKY and USDS to Its Trading Platform
More in DeFi on MM Crypto Analysis Web.
Pingback: Acala Karura Sunset Set for February 10, 2027