KelpDAO Bridge Incident: Aave’s Loss Scenarios and the DVN Configuration Question

Reported on April 21, 2026, at 17:25 (UTC+8). This article reflects the information available in the original report, not a current assessment of the incident.

Aave’s potential losses from the KelpDAO cross-chain bridge incident depended on a question the report had not resolved: who would absorb the shortfall in rsETH? An incident report cited by PA News said an attacker forged a cross-chain message to release approximately 116,500 rsETH, then deposited 89,600 rsETH into Aave as collateral and borrowed roughly $190 million in ETH and related assets.

Exposure depends on how the shortfall is allocated

According to the cited Aave report, distributing the loss across all rsETH holders could leave rsETH approximately 15% below its peg and produce about $123 million in Aave bad debt. Concentrating the loss on Layer 2 networks instead could raise the estimated bad debt to approximately $230 million, chiefly on networks including Arbitrum and Mantle. These were scenarios, not confirmed losses.

Aave said it had frozen rsETH markets and set its loan-to-value ratio to zero. In a separate update, it said the WETH reserve on Ethereum Core V3 had been unfrozen, allowing new WETH supply, while its WETH loan-to-value ratio remained zero. WETH reserves on Ethereum Prime, Arbitrum, Base, Mantle and Linea remained frozen.

Lido said its EarnETH vault had roughly $21.6 million of direct rsETH exposure through an Aave rsETH/ETH leveraged position. It said deposits and withdrawals were paused, a $3 million first-loss protection mechanism was available if needed, and its core stETH and wstETH staking protocols were unaffected.

A wider verification-design question

Dune Analytics said its analysis of approximately 2,665 distinct LayerZero OApp contracts active over the 90 days preceding its April 2026 report found that 47% used a 1-of-1 DVN configuration—one required decentralized verifier network—including KelpDAO’s rsETH application. Another 45% used 2-of-2, and approximately 5% used 3-of-3 or higher configurations. These figures describe configurations, not an independent estimate of how many applications were exploitable.

Separately, PA News reported that the Arbitrum Security Council had frozen approximately 30,766 ETH associated with the attacker. The funds could not be accessed from their previous addresses; a further transfer would require Arbitrum governance action and coordination with relevant parties.

Source: panewslab.com (originally published 2026-04-21 17:25 UTC+8)

Further reading