Aave froze WETH collateral across six markets as the rsETH crisis spread

Aave’s risk service providers disclosed on April 19, 2026, that the Protocol Guardian had frozen wrapped ether as collateral across six Aave V3 markets. The action covered Ethereum Core, Ethereum Prime, Arbitrum, Base, Mantle and Linea and prevented users from opening new borrows against WETH collateral while the protocol monitored fallout from the Kelp DAO rsETH incident.

The measure widened Aave’s response beyond rsETH itself. On April 18, the Guardian had already frozen rsETH and wrapped rsETH markets across Aave deployments, while Aave’s V4 security council disabled new supply and borrowing against rsETH. The April 19 WETH action showed that a failure originating in cross-chain verification could force restrictions on a much more widely used DeFi collateral asset.

What Aave changed

A freeze is narrower than deleting a market or declaring deposited WETH lost. Aave’s event-day record said the change stopped new borrowing against WETH collateral in the six named markets. It did not say that WETH’s token contract had failed, that ether itself had been compromised or that all Aave pools had stopped operating.

That distinction mattered because the original trigger sat elsewhere. Kelp said a forged cross-chain packet had been accepted by bridge-verification infrastructure on April 18, releasing 116,500 rsETH from an Ethereum bridge lockbox to an attacker-controlled address. Kelp maintained that its Ethereum restaking assets, rsETH contract and underlying EigenLayer deposits remained intact, while warning that holders of wrapped rsETH on layer-two networks faced a separate impact assessment.

A single verifier became the fault line

LayerZero’s April 19 incident statement said Kelp’s relevant application route used a one-of-one Decentralized Verifier Network configuration, with the LayerZero Labs DVN acting as the sole verifier. LayerZero attributed the false attestation preliminarily to poisoned downstream RPC infrastructure combined with denial-of-service pressure against uncompromised RPCs. It said this caused its DVN to confirm transactions that had not occurred.

Those were contemporaneous findings from an infrastructure provider involved in the incident, not an independent final forensic determination. LayerZero also made a preliminary attribution to a likely North Korean state actor. That attribution remained unproven in the event-day public record and is not needed to establish Aave’s defensive action.

Blockaid’s April 19 analysis independently confirmed from the bridge configuration and transaction path that the route required one DVN and no optional DVNs. It reported that the forged message caused the adapter to release 116,500 rsETH and that a later packet seeking another 40,000 rsETH failed after Kelp’s emergency pause. The figures are token quantities observed in the transaction path, not estimates of recovered value or final loss.

Why the freeze mattered

The episode exposed composability as both DeFi’s utility and its transmission mechanism. A token created for liquid restaking could move through a bridge, become collateral in a lending market and affect borrowing conditions for WETH across several networks. Smart contracts can operate according to their configured rules while the combined system still accepts a false premise supplied by compromised off-chain verification.

For institutions assessing DeFi, the April 19 response made security architecture inseparable from collateral policy. A lending protocol’s exposure depended not only on its own code but also on the verifier set, bridge escrow and operational controls behind an admitted asset. A one-of-one configuration converted one compromised verification path into a system-wide assumption.

What remained unresolved

As of April 19, Aave had not published a final accounting of any deficit in the cited event-day record. Kelp had not announced completed migration terms for layer-two holders, and the involved parties had not produced a joint final root-cause report. The verified development was therefore the six-market WETH collateral freeze and the preliminary technical explanation around it—not a final loss allocation, recovery outcome or legal attribution.