# KelpDAO Sues LayerZero and Its Co-Founder Over the $292 Million rsETH Bridge Exploit

The suit alleges LayerZero reviewed and endorsed the single-verifier configuration that attackers abused, then blamed Kelp publicly. Bryan Pellegrino calls the claims meritless.

- Published: 2026-09-25T13:11:38.958Z
- Canonical: https://polylog.news/crypto/2026-09-25/kelpdao-sues-layerzero-and-its-co-founder-over-the-292-milli
- Publisher: Polylog (Crypto desk)
- Section: crypto
- Sources: [CoinDesk](https://www.coindesk.com/business/2026/09/25/kelpdao-sues-layerzero-for-the-largest-exploit-2026-has-seen-so-far), [Polylog editors](https://polylog.news), [The Block](https://www.theblock.co/news/regulation/2026-09-25-kelpdao-sues-layerzero-claims-it-endorsed-setup-used-in-292-million-rseth-exploit-416361)

KelpDAO, the operator of the restaking token rsETH, sued LayerZero and its co-founder Bryan Pellegrino over the April 18 exploit that drained 116,500 rsETH, worth roughly $292 million at the time. The complaint alleges negligent misrepresentation, negligence and defamation, and claims LayerZero [failed to disclose weaknesses in its own messaging setup](https://www.coindesk.com/business/2026/09/25/kelpdao-sues-layerzero-for-the-largest-exploit-2026-has-seen-so-far) while reviewing and endorsing the configuration Kelp used.

The attack path was not a contract bug. According to reporting on the filing, an attacker used social engineering in early March to install malware on a LayerZero developer's machine, then tampered with LayerZero remote procedure call nodes and hit an outside provider with a denial-of-service attack, so that LayerZero's decentralized verifier network [approved a forged message](https://www.theblock.co/news/regulation/2026-09-25-kelpdao-sues-layerzero-claims-it-endorsed-setup-used-in-292-million-rseth-exploit-416361). The verifier signed what it was shown. Kelp's argument is that LayerZero knew a single-verifier configuration could be defeated that way and approved it anyway.

Pellegrino has called the lawsuit meritless and said he will defend himself and the company in a British Columbia court. Cointelegraph reported the filing as an allegation that LayerZero's [security failures caused the exploit](https://t.me/cointelegraph/72317). Kelp says users have withdrawn more than $650 million since April and that it committed 2,000 ETH toward restoring rsETH's backing.

Both sides have an obvious interest. Kelp needs to shift the loss and repair its reputation with depositors. LayerZero needs to preserve the claim that its verifier design is sound and that integrators choose their own configurations. The case will test whether an interoperability provider that reviews a client's setup carries legal duty when that setup fails.

## What this means

The mechanism at issue is liability allocation for trusted off-chain components, and the exposed parties are cross-chain messaging providers, restaking issuers and the depositors who assumed "audited" covered the verifier set. If a court lets a negligent-misrepresentation claim proceed against a middleware provider for endorsing a configuration, the cost of offering integration advice rises immediately, and providers respond by publishing disclaimers, mandating minimum verifier thresholds, and refusing to bless customer setups. The precedent worth naming is the wave of post-2022 bankruptcy litigation, where recovery efforts migrated from on-chain forensics to courtrooms and reshaped counterparty documentation. The likelier outcome over the next several months is more suits of this kind by protocols against their infrastructure vendors, and contractual hardening of security-review relationships, well before any judgment lands. The read depends on the British Columbia action surviving early procedural challenge. It would be undercut if the case is dismissed or quietly settled with no disclosure, which would leave informal blame allocation intact.

## What to watch

- Whether the court allows the negligent-misrepresentation count to proceed, which sets the template for future claims against messaging and oracle providers.
- Whether LayerZero changes default verifier requirements for large integrations, the practical fix for a single-signer failure mode.
- Whether rsETH deposits stabilize, the measure of how much of Kelp's damage is legal rather than commercial.