Ripple CTO: Kelp DAO Exploit Reflects Bridge Security Trade-Offs

ZRO0,49%

David Schwartz, CTO Emeritus at Ripple, identified a pattern in bridge security vulnerabilities after the Kelp DAO rsETH bridge was exploited for approximately $292 million. During his evaluation of DeFi bridging systems for RLUSD use, Schwartz observed that bridge providers consistently deprioritized their most robust security mechanisms in favor of convenience, a pattern he believes may have contributed to the Kelp DAO incident.

The Security Features Sales Pitch

In his analysis shared on X, Schwartz described how bridge providers pitched advanced security features prominently, then immediately suggested those features were optional. “They generally in effect recommended not bothering to use the most important security mechanisms because they have convenience and operational complexity costs,” he wrote.

Schwartz noted that during RLUSD evaluation discussions, providers emphasized simplicity and ease of adding multiple chains “with the implicit assumption we wouldn’t bother using the best security features they had.” He summarized the contradiction: “Their sales pitch was that they have the best security features but they’re easy to use and scale, assuming you don’t use the security features.”

What Happened to Kelp DAO

On April 19, Kelp DAO identified suspicious cross-chain activity involving rsETH and paused contracts across mainnet and multiple Layer 2 networks. Approximately 116,500 rsETH was drained through LayerZero-related contract calls, worth around $292 million at current prices.

On-chain analysis from D2 Finance traced the root cause to a private key leak on the source chain, which created a trust issue with OApp nodes that the attacker exploited to manipulate the bridge.

LayerZero Security Configuration

LayerZero itself offers robust security mechanisms, including decentralized verification networks. Schwartz hypothesized that part of the problem may stem from Kelp DAO choosing not to use key LayerZero security features “out of convenience.”

Investigators are examining whether Kelp DAO configured its LayerZero implementation using a minimal security setup—specifically, a single point of failure with LayerZero Labs as the sole verifier—rather than utilizing the more complex but significantly more secure options available through the protocol.

Disclaimer: The information on this page may come from third parties and does not represent the views or opinions of Gate. The content displayed on this page is for reference only and does not constitute any financial, investment, or legal advice. Gate does not guarantee the accuracy or completeness of the information and shall not be liable for any losses arising from the use of this information. Virtual asset investments carry high risks and are subject to significant price volatility. You may lose all of your invested principal. Please fully understand the relevant risks and make prudent decisions based on your own financial situation and risk tolerance. For details, please refer to Disclaimer.

Related Articles

Volo Protocol Loses $3.5M in Sui Hack, Commits to Absorb Losses and Freeze Hacker Funds

Gate News message, April 22 — Volo Protocol, a yield vault operator on Sui, announced yesterday (April 21) that it has begun freezing stolen assets following a $3.5 million exploit. Hackers looted WBTC, XAUm, and USDG from Volo Vaults, marking the latest major DeFi security breach in a

GateNews3h ago

French Family Forced to Transfer $820K in Crypto After Armed Home Invasion

Gate News message, April 22 — A family in Ploudalmézeau, a small town in Brittany, France, was invaded by two armed masked men on Monday (April 20), according to reporting by The Block. Three adults were bound for over three hours and forced to transfer approximately 700,000 euros (about $820,000) i

GateNews4h ago

DOJ Launches Compensation Process for OneCoin Fraud Victims, $40M+ in Recovered Assets Available

Gate News message, April 22 — The U.S. Department of Justice has announced the launch of a compensation process for victims of the OneCoin cryptocurrency fraud scheme, with more than $40 million in recovered assets now available for distribution. The scheme, operated between 2014 and 2019 by Ruja

GateNews5h ago

AI16Z, ELIZAOS Creators Sued Over $2.6B Fraud Allegations; Token Crashes 99.9% From Peak

Federal class action accuses AI16Z/ELIZAOS of a $2.6B crypto fraud via fake AI claims and deceptive marketing, alleging insider favoritism and a staged autonomous system; seeks damages under consumer protection laws. Abstract: This report covers a SDNY federal class-action filed April 21 accusing AI16Z and its rebrand ELIZAOS of a $2.6 billion crypto fraud involving fake AI claims and deceptive marketing. The suit alleges a manufactured link with Andreessen Horowitz and a non-autonomous system. It details a peak valuation in early 2025, a 99.9% crash, and about 4,000 losing wallets, with insiders receiving ~40% of new tokens. Plaintiffs seek damages and equitable relief under New York and California consumer-protection laws. Regulators in Korea and major exchanges have warned or suspended related trading.

GateNews6h ago

SlowMist Alerts: Active MacSync Stealer macOS Malware Targeting Crypto Users

SlowMist warns of MacSync Stealer (v1.1.2) for macOS that steals wallets, credentials, keychains, and infra keys, using spoofed AppleScript prompts and fake 'unsupported' errors; urges caution and awareness of IOCs. Abstract: This report summarizes SlowMist's alert about MacSync Stealer (v1.1.2), a macOS information stealer targeting cryptocurrency wallets, browser credentials, system keychains, and infrastructure keys (SSH, AWS, Kubernetes). It deceives users with spoofed AppleScript dialogs prompting for passwords and visible fake 'unsupported' messages. SlowMist provides IOCs to customers and advises avoiding unverified macOS scripts and remaining vigilant for unusual password prompts.

GateNews7h ago

North Korean Lazarus Group Deploys Mach-O Man Malware to Steal Crypto Wallet Credentials from macOS Users

Lazarus releases Mach-O Man for macOS to steal keychain data and wallet credentials, targeting crypto executives via ClickFix pop-ups and compromised Telegram meetings. Abstract: The article reports that the Lazarus-linked Mach-O Man malware targets macOS to exfiltrate keychain data, browser credentials, and login sessions to access cryptocurrency wallets and exchange accounts. Distribution relies on ClickFix social engineering and compromised Telegram accounts directing victims to fake meeting links. The piece ties the operation to the April 20 Kelp DAO hack and identifies TraderTraitor as Lazarus-affiliated, noting rsETH movement across blockchains via LayerZero’s OFT standard.

GateNews8h ago
Comment
0/400
LateBlockLarryvip
· 10h ago
Once safety is treated as optional in infrastructure like bridges, it becomes a disaster site where money is burned by the second. When convenience and safety must be chosen between, the project team should always choose the latter.
View OriginalReply0
Glass-HeartMarketMakervip
· 04-21 13:12
Private key leakage + simplifying security options for "ease of use"—no matter how strong LayerZero is, it can't withstand this kind of setup. The risks of bridges are often amplified by human factors.
View OriginalReply0
FoldedCosmosCatvip
· 04-20 04:06
292M This tuition is too expensive...
View OriginalReply0
0xNapvip
· 04-20 03:36
The probability of LayerZero being blamed has increased again; the root cause is still key management plus overly simplified security configurations. Don't treat default settings as security configurations.
View OriginalReply0
SummerNightColdWalletvip
· 04-20 03:28
Hopefully this time we can push the industry to unify some minimum security baselines for bridges: multi-signature/threshold, hardware isolation, decentralized approval, rollback/pause mechanisms, otherwise the next Kelp is just a matter of time.
View OriginalReply0
ColdBrewSparklingWatervip
· 04-20 03:25
说白了还是图省事出大事。
Reply0
OnchainComplainervip
· 04-20 03:16
The moment security features are "optimized away," a hidden danger is planted.
View OriginalReply0
MevStreetPhotographervip
· 04-20 03:16
I recall a saying: Cross-chain bridges are not a coding issue, but an operational security issue. Private key management, permission isolation, threshold signatures, audit alerts—these are much more important than "quick deployment."
View OriginalReply0