KelpDAO Suffers $292M Exploit, DeFi TVL Plunges

KelpDAO lost $292 million in a bridge exploit that drained liquidity and triggered a $13 billion decline in DeFi total value locked. The attack targeted KelpDAO's wrapped-stake token, rsETH, via a vulnerability in the LayerZero cross-chain messaging path, creating cascading solvency pressure across lending protocols including Aave. Separately, cloud host Vercel confirmed a supply-chain compromise of a third-party AI tool that exposed developer credentials; CEO Guillermo Rauch said "highly sophisticated" actors appear to have used AI-assisted techniques to expand access. Projects are performing immediate credential rotations, emergency parameter fixes, and onchain mitigations. The incident highlights persistent bridge risk, composability fragility in DeFi, and a rising class of attacks that combine supply-chain compromises with AI-enabled automation.
What happened
KelpDAO suffered a loss of $292 million after attackers exploited a bridge vulnerability, draining liquidity from the DAO and its wrapped staking token, `rsETH`. The exploit is tied to the LayerZero messaging/bridge component that KelpDAO used to move assets across chains. The market reaction was immediate, with DeFi total value locked falling roughly $13 billion and lending protocols such as Aave showing increased bad debt and solvency stress. Independently, cloud host Vercel confirmed a security incident traced to a compromised third-party AI tool; CEO Guillermo Rauch said the adversary was "highly sophisticated" and used AI-assisted tactics to escalate access and harvest credentials used by Web3 teams.
Technical details
The attack chain combined a cross-chain message manipulation in LayerZero with downstream logic in KelpDAO's contracts for rsETH. LayerZero is a messaging layer that many protocols use for cross-chain transfers; when its guarantees are violated attackers can forge messages or replay states to cause mis-accounting on the recipient chain. Practitioners should note these technical characteristics:
- •The root cause appears to be a trust boundary failure in cross-chain message validation rather than an EOA private key compromise.
- •rsETH minting and redemption logic relied on bridge invariants that became invalid under crafted messages, allowing attacker-created supply.
- •The incident produced rapid market liquidations and inter-protocol contagion due to composable collateral positions, increasing onchain slippage and oracle-led mispricings.
Immediate operational responses from teams include:
- •Bulk credential rotations and secrets revocation by projects hosted on Vercel after the supply-chain AI tool compromise.
- •Emergency governance oracles being paused and bridge endpoints blacklisted or rate-limited.
- •Liquidity rescues and debt auctions initiated by affected lending platforms.
Context and significance
This event stitches together two escalating trends. First, bridges remain the largest systemic risk in DeFi because they centralize cross-chain finality assumptions and give outsized power to messaging layers like LayerZero. Second, the Vercel incident shows supply-chain attacks can cascade into Web3 when developer infrastructure and CI/CD tooling are targeted. The additional claim that attackers used AI to assist intrusion matters for defenders because it changes the threat model: AI can accelerate reconnaissance, generate targeted credential-phishing content at scale, and optimize exploit sequences faster than manual actors. The combination of automated reconnaissance plus a bridge semantic bug produced high-velocity damage and a broader market shock.
Why practitioners should care
Smart contract developers must assume bridge messages can be forged and code defensively: assert canonical state on-chain, add multi-signature or delay windows for cross-chain mints, and harden invariant checks for token supply. DevOps and security teams must treat third-party AI tools and developer platforms as high-risk dependencies. Attack surface reductions should include principle-of-least-privilege for environment variables, automated secret scanning, and routine rotation of deploy keys.
What to watch
Law enforcement and cross-chain teams will investigate attribution, while protocol maintainers will push emergency patches and harden bridging logic. Monitor LayerZero advisories, KelpDAO governance proposals, and Vercel incident updates for credential audit results. The episode will accelerate two trends: adoption of bridge postures that include time-locks and guardians, and enterprise-style security controls around AI tool integrations.
Bottom line
The KelpDAO-$292M exploit is an inflection point for DeFi risk management. It demonstrates that protocol composability and developer supply chains are single-fault domains. Expect immediate hardening, more conservative bridge designs, and elevated scrutiny of AI-driven tooling integrations across Web3.
Scoring Rationale
Large-scale financial loss plus a systemic TVL shock makes this a major security event. The novel element is the reported AI-assisted, supply-chain component, which raises the threat model for Web3 and developer tooling.
Practice with real Telecom & ISP data
90 SQL & Python problems · 15 industry datasets
250 free problems · No credit card
See all Telecom & ISP problemsStep-by-step roadmaps from zero to job-ready — curated courses, salary data, and the exact learning order that gets you hired.



