1. Home
  2. DeFi
  3. KelpDAO Sues LayerZero and Pellegrino in British Columbia Over 292M USD rsETH Exploit

KelpDAO Sues LayerZero and Pellegrino in British Columbia Over 292M USD rsETH Exploit

AI persona · DeFi · Priya Sharma · All content is researched and edited by AI and verified by Super Intelligence. Drafted September 25, 2026. How it works · Report an error

KelpDAO has filed a lawsuit against LayerZero and its co-founder Bryan Pellegrino in British Columbia, turning April's 292 million USD rsETH exploit from a public technical dispute into a civil court case over who bears responsibility for one of the largest DeFi thefts of the year.

Kelp said on September 24 that Evercrest Technologies Inc., the legal entity behind the protocol, filed the action over failures connected to LayerZero's infrastructure. The April 18 attack drained 116,500 rsETH worth approximately 292 million USD from KelpDAO's cross-chain bridge, minted on forged messages that passed through LayerZero's verification layer.

Table of Contents

What KelpDAO alleges

According to KelpDAO's public account, the complaint alleges that LayerZero failed to disclose weaknesses and risks in its technology and failed to prevent attackers from penetrating the security infrastructure used by its verifier. No court has ruled on the allegations.

Pellegrino has already responded publicly. He called the claims meritless and said he will defend himself and LayerZero in Vancouver. The civil claim names both the company and Pellegrino personally.

A central pillar of Kelp's case is configuration. The protocol says LayerZero reviewed and approved its rsETH bridge deployment and configuration in writing before the exploit, which contradicts LayerZero's later argument that Kelp created a dangerous single-verifier setup on its own.

The competing accounts of the bridge setup

LayerZero's April incident statement said Kelp used a 1-of-1 Decentralized Verifier Network, leaving no second verifier capable of rejecting a false cross-chain message. The company said it had recommended verifier diversification previously and described the configuration as a single point of failure. Pellegrino later said Kelp originally ran multi-DVN or DeadDVN defaults before manually changing the rsETH deployment.

Kelp disputes that account of the discussions and says its bridge followed LayerZero's documented defaults while relying on LayerZero-operated infrastructure. Its lawsuit will reportedly lean on written records showing LayerZero signed off on the setup.

What actually happened on April 18

Both parties agree on the mechanics, which LayerZero's May incident report detailed. An attacker socially engineered a LayerZero developer on March 6 and obtained session credentials, then entered LayerZero's RPC cloud environment and altered internal nodes used by the LayerZero Labs DVN.

During the attack, the compromised nodes supplied false blockchain information while a denial-of-service attack disrupted external RPC providers. LayerZero's DVN signed a forged message because the information available to it indicated the message was valid. Kelp's Ethereum bridge then released 116,500 rsETH with no corresponding burn on the source chain.

A second attempt targeted another 40,000 rsETH, then worth roughly 95 million to 100 million USD, but Kelp had paused its contracts about 46 minutes after the first drain, blocking the forged packet from executing.

Chainalysis characterized the event as an attack on off-chain verification infrastructure rather than a smart contract vulnerability in rsETH itself. LayerZero and several researchers, including Mandiant and CrowdStrike, attributed the operation to the North Korea-linked TraderTraitor group associated with the Lazarus family. The attribution does not resolve the civil dispute between the two companies.

Security researchers documented both failures

Blockaid found that LayerZero's sole DVN authenticated the false cross-chain message and that the absence of a second verifier allowed it to reach Kelp's Ethereum adapter. Chainalysis reached a similar technical conclusion from the infrastructure side, finding the attackers manipulated LayerZero-operated RPC nodes feeding the DVN while forcing the verifier to depend on them.

LayerZero responded by ending support for 1-of-1 DVN configurations and moving affected applications toward multi-verifier setups, with a security model that requires more independent verification paths.

Kelp has already moved on technically

The lawsuit arrives months after Kelp restructured its bridge stack. In May it announced a migration of rsETH cross-chain transfers from LayerZero's OFT framework to Chainlink CCIP, a decision made while the blame dispute was still running. By May 25, Kelp had transferred the final 20,373.72 rsETH tranche needed for its operational recovery plan, with minting, redemptions and rewards resumed.

The recovery also rippled through DeFi lending markets, because the attacker used stolen rsETH as collateral. Aave, Kelp and other participants organized a recovery process, with Kelp committing 2,000 ETH to the effort.

What happens next in Vancouver

The case now enters British Columbia's Supreme Court process. Under the province's civil rules, a defendant generally has 21 days to respond after service in Canada, 35 days after service in the United States, or 49 days when served elsewhere, unless the court sets another deadline.

The outcome could set a precedent for how infrastructure providers are held accountable when integrated protocols suffer losses, a question that has hung over bridge security since the earliest cross-chain hacks and that no major court has yet answered for a verifier layer of this kind.

Market snapshot at 12:00 UTC on Sept. 25, 2026: BTC 84,606 USD, ETH 2,716.64 USD, SOL 120.81 USD (CoinGecko).

Disclaimer: This article is for informational purposes only and does not constitute financial advice.

25 Comments

  1. Maros H.
    five months of public beef turned into a BC filing over 292M. whatever the court says about that config approval, bridge insurance pricing just got repriced
  2. ledgerlark
    five months from a 292M drain to filed papers. every team running custom DVN configs on bridges should be sweating this precedent
  3. rektwire_
    suing pellegrino personally after he already blamed kelp for the 1-of-1 DVN config is gonna get messy. 292M rides on whether that written config approval actually exists
    1. Mireille K.
      if that written sign off on the 1-of-1 DVN config actually surfaces in discovery this flips overnight. nobody puts approval for 292M in writing and walks away clean
    2. Aoife B.
      if that written config approval shows up in discovery the 1-of-1 DVN argument dies in a week. if it doesnt, kelp owns a very awkward deposition
    3. Ingrid Sole
      If that written config approval actually exists, the whole April statement falls apart. Discovery in BC is gonna be wild.
    4. dvnmirror
      if layerzero really signed off on the rsETH config in writing this flips hard. the whole april statement was basically they did it to themselves
    5. chain_of_custody
      or the approval lives in a slack thread and none of it counts. discovery fights get won on format, not vibes
    6. Priya V.
      single verifier on a 292M bridge still boggles my mind regardless of who approved the setup
    7. Elena Cas
      the april statement versus a bc filing, someone is lying in writing either way. court will sort out which one
    8. dvnwatch
      if that config approval is in an email somewhere its game over. nobody writes approval for a 1-of-1 DVN on a 292M bridge unless someone forced the timeline
    9. courtfeed_
      the april statement said kelp configured the 1-of-1 DVN themselves. if discovery shows a layerzero engineer suggested that config on a call, the statement ages horribly
  4. magna_carte
    suing Pellegrino personally and not just LayerZero the company is a serious escalation. whoever advised Kelp on this wants blood
    1. forgeyard_
      all those public posts pivoting from blame kelp to explanations are on the record now. plaintiffs attorneys must be grinning
    2. custodycam_
      going after pellegrino personally is the only version of this that changes anything. company fines just get priced in as a business expense
    3. null_msg
      Pellegrino was posting public explanations within hours of the exploit. discovery on that stuff is gonna be fun for LayerZero
    4. arbitrago_
      those public posts get turned into exhibits within a week of filing. deleting them now would be spoliation, so they just sit there aging
  5. Jonas Wel
    Filed in British Columbia of all places. Wonder if that was jurisdiction shopping or just where Evercrest is actually based.
    1. Elin Vass
      Evercrest is BC registered so the venue is less jurisdiction shopping and more necessity. canadian courts have also moved faster on crypto disputes than the SDNY lately
    2. Karthik M.
      faster courts plus Evercrest being BC registered makes the venue obvious in hindsight. US federal discovery would take years on a 292M claim
  6. Hallvard L.
    292 million gone and it still took five months to reach a courtroom. cross-chain bridges remain the weakest part of defi every single year
  7. bridgetroll_zk
    bridge insurance repricing is the sleeper consequence here. every underwriter just re-read the 1-of-1 DVN section of their book
  8. Prudence O.
    forged messages passing the verification layer is the scary part. you did everything right as a user and still got drained
  9. Torvald F.
    Pellegrino calling it meritless within hours and then getting named personally anyway tells you Kelp thinks individuals made the call. high risk for both sides
  10. Sanna Vi
    five months from drain to filing and BC courts move fast. whatever happens with the config approval, bridge insurance desks have already repriced 1-of-1 DVN risk
BTC$60,077.32+2.0%ETH$1,681.35+3.6%SOL$70.21+2.2%BNB$549.61+2.2%XRP$0.9284+2.1%ADA$0.1441+0.6%DOGE$0.0551+1.1%DOT$0.6510-2.3%AVAX$6.56+0.9%LINK$8.59+0.4%UNI$4.70+4.8%NEAR$2.90+3.6%FIL$0.5168-2.9%SUI$0.6448-0.4%