Crypto News

Aave Sheds $6 Billion in TVL After KelpDAO Hack Exposes Structural Risk

Published: Apr 19, 2026By SpendNode Editorial

Key Analysis

Aave's total value locked fell by $6 billion in days after the KelpDAO bridge drain, exposing how liquid restaking collateral can turn a niche exploit systemic.

Aave Sheds $6 Billion in TVL After KelpDAO Hack Exposes Structural Risk

Aave's total value locked has dropped by roughly $6 billion since the KelpDAO bridge drain last week, according to a CoinDesk report published April 19. The exodus is more than 20 times the size of the $292 million bridge exploit that started the chain reaction, and it is forcing a public conversation about how DeFi's largest lender accepts liquid restaking tokens as collateral.

As of April 19, ETH was trading at $2,340, down 1.1% on the day, while BTC sat at $76,047. AAVE the token has already taken a 22% leg down this week as whales rotated out, but the TVL number is a different signal. It shows depositors leaving the protocol, not just speculators selling the governance asset.

From a Single Bridge Exploit to a $6 Billion Capital Flight

The original incident was narrow. A LayerZero-based bridge operated by KelpDAO was drained for about $292 million on April 15, almost all of it in rsETH, the project's liquid restaking token. Aave is one of the main venues where rsETH has been used as collateral, and the protocol paused new rsETH borrows within hours of the incident becoming public.

The pause stopped new risk from building. It did not stop lenders and looping strategies from pulling the collateral they already had at work. Over the following four days, TVL measurements aggregated across Aave's v3 markets fell by around $6 billion, with the sharpest outflows on Ethereum mainnet.

Two things usually drive a drop of this size. The first is direct de-risking: depositors unwinding staking and yield positions they no longer trust to behave predictably. The second is forced mechanical deleveraging as looped trades unwind. A recursive deposit and borrow against rsETH, for example, has to collapse as soon as the collateral leg stops earning or becomes hard to exit. Both have been visible this week.

Why This Reads as Structural and Not One-Off

Aave has weathered larger dollar exploits before without a TVL move of this magnitude. The difference this time is the type of asset at the center. Liquid restaking tokens sit on top of another layer of infrastructure, the bridge, the restaking protocol, the underlying validator set, and a failure at any of those layers leaks back into the lender that accepts the wrapped receipt as collateral.

That is the "structural" part of the CoinDesk headline. A lender's balance sheet stops being a function of its own risk parameters the moment it accepts a token whose value depends on a protocol it does not control. When rsETH holders lost faith in the peg, Aave's rsETH markets became an exit door, and Aave had to absorb the volatility whether or not its own contracts had any vulnerability.

Competing lenders are reading the same tape. Spark and Morpho have both been asked in governance channels to review their LRT listings. The open question is whether DAO risk committees tighten caps and haircuts on LRT collateral across the board, or whether LRTs get quietly sidelined on the largest lenders the way algorithmic stablecoins were after Terra.

What It Means for Deposits and Yield Strategies

For users who treat Aave as a base layer for passive yield, the immediate change is that headline APRs on ETH and stablecoin pools have moved. Borrow demand around rsETH has vanished, and the utilization swings are showing up in supply rates. Anyone who had set-and-forget positions against LRT collateral is either out or in the middle of unwinding.

The longer-term read matters more for anyone using DeFi as a spending backstop. A growing number of wallets top up spend from your own wallet setups by drawing a stablecoin credit line against ETH or LSTs on Aave. When the lender's collateral book is in flux, those credit lines get repriced and sometimes suspended. The pause on new rsETH borrows is the live example this week. If risk committees extend similar treatment to other LRTs, debit-style crypto spending flows that depend on those lines will feel it before the price charts do.

The CoinDesk figure is the snapshot the market is watching. The number that will determine whether this becomes a permanent reset or a dip is the one nobody has published yet: how much of the $6 billion comes back after the KelpDAO post-mortem lands.

Overview

Aave has lost roughly $6 billion in TVL in the four days since the KelpDAO bridge exploit. The outflow is more than 20 times the $292 million headline loss from the original hack and it is concentrated in markets where rsETH served as collateral. The episode is a lesson about second-order risk in DeFi lending: a protocol that accepts wrapped derivatives of other protocols absorbs their problems. AAVE token is down 22% on the week, ETH is at $2,340, and risk committees across DeFi are about to revisit how much weight LRTs should carry on lender balance sheets.

Frequently Asked Questions

Is Aave itself at risk of insolvency?

No public on-chain data suggests Aave's own contracts are compromised. The drop is depositors withdrawing, not bad debt. The risk is indirect: LRT collateral exposure that the protocol cannot fully de-risk without cooperation from the underlying restaking protocol.

Did Aave get hacked?

No. The exploit was at KelpDAO's LayerZero bridge. Aave's exposure is as a venue that accepts rsETH as collateral. Its smart contracts have not been reported to be vulnerable.

Does this affect crypto card users?

Only indirectly. Cards that are funded by drawing credit lines against DeFi collateral can see rate and availability changes when a major lender's risk parameters shift. Cards that run on simple custodial balances or stablecoin rails are unaffected.

DisclaimerThis article is provided for informational purposes only and does not constitute financial advice. All fee, limit, and reward data is based on issuer-published documentation as of the date of verification.

Have a question or update?

Discuss this analysis with the community on X.

Discuss on X

Comments

Comments are moderated and may take a moment to appear.