April 18 was not just a Kelp-specific issue.

The incident originated at the infrastructure layer. A forged cross-chain message, linked to compromised LayerZero RPC nodes, resulted in a $292M rsETH drain.
The response is what shaped the outcome.
Kelp detected the anomaly promptly and paused contracts across Ethereum and multiple L2s within an hour.
They blacklisted the exploiter’s wallets and engaged SEAL-911 to coordinate mitigation across ecosystem participants.
These actions prevented a second exploit attempt worth $95M.
Arbitrum’s Security Council also intervened and secured $71M from the exploiter.
There was no broader contagion into lending markets and no systemic disruption across DeFi.
This underscores a larger point.
Shared infrastructure risk is becoming a critical consideration, as reflected in Dune data showing a significant number of OApps operating with similar configurations.
While the incident itself was material, the response was measured and effective.
In situations like this, execution under pressure directly influences outcomes.