📈 Get daily crypto insights that make you smarter about your money

Kelp DAO Suffers $292 Million Bridge Exploit Through Off-Chain Infrastructure Attack

The decentralized finance ecosystem faced another devastating blow on February 28, 2025, as Kelp DAO confirmed a massive $292 million exploit targeting its cross-chain bridge. Unlike typical smart contract vulnerabilities that have plagued DeFi protocols in recent years, this attack exposed a critical weakness in off-chain infrastructure — a growing blind spot that the industry can no longer afford to ignore. With Bitcoin trading at approximately $84,373 and Ethereum at $2,238 on the day of the attack, the broader crypto market was already reeling from the aftermath of the $1.5 billion Bybit hack just one week earlier.

The Exploit Mechanics

Blockchain analytics firm Chainalysis conducted a thorough investigation and confirmed that the Kelp DAO exploit was not caused by a smart contract bug. Instead, the attacker manipulated the protocol’s off-chain relay and validation systems to mint rsETH tokens without providing any real collateral. The bridge’s backend infrastructure, which validates cross-chain transactions, was compromised through a sophisticated multi-step process.

According to the Chainalysis report, the attack unfolded in five distinct stages. First, the attacker conducted reconnaissance on the bridge’s off-chain relay system, identifying weaknesses in the validation process. Second, they gained unauthorized access to the off-chain infrastructure, likely by exploiting a vulnerability in a server or API endpoint. Third, they submitted a fabricated proof of asset burn that the off-chain relay accepted without proper verification. Fourth, the bridge minted approximately 10,000 rsETH tokens on the destination chain with zero backing. Finally, the attacker swapped the unbacked rsETH for other assets and routed the funds through mixers and exchanges to obscure the trail.

The total value drained reached approximately $292 million, making it one of the largest DeFi exploits in history. The attacker created rsETH tokens essentially out of thin air by compromising the backend validation layer rather than exploiting any on-chain logic.

Affected Systems

The primary system affected was the Kelp DAO bridge, which facilitates cross-chain transfers of rsETH — a liquid restaking token that represents staked Ethereum positions. The bridge relies on off-chain relays to verify that assets have been locked or burned on the source chain before minting equivalent tokens on the destination chain. This trust assumption proved to be the fatal vulnerability.

The exploit also had cascading effects on the broader liquid restaking ecosystem. RsETH holders faced uncertainty about the token’s backing, and several decentralized exchanges temporarily paused rsETH trading pairs as a precautionary measure. The incident raised concerns about the security of other liquid restaking protocols that employ similar off-chain validation mechanisms, including protocols managing billions in total value locked across Ethereum’s restaking landscape.

The Mitigation Strategy

In the immediate aftermath, Kelp DAO’s team took several steps to contain the damage. The bridge was paused to prevent further unauthorized minting, and on-chain monitoring systems were deployed to track the movement of stolen funds. The protocol team began coordinating with major exchanges and blockchain analytics firms to flag and freeze any stolen assets that reached centralized platforms.

Chainalysis recommended that bridge protocols implement mandatory on-chain verification of burn and lock events, eliminating the single point of failure that off-chain relays represent. Additional mitigation measures include multi-signature requirements for relay operations, real-time anomaly detection systems that flag unusual minting patterns, and regular penetration testing of both on-chain and off-chain components. The firm also emphasized the need for decentralized oracle networks to provide independent verification of cross-chain state changes.

Lessons Learned

The Kelp DAO exploit underscores a fundamental shift in attack vectors within the crypto space. As smart contract auditing has matured and on-chain code has become more battle-tested, attackers are pivoting toward the softer targets of off-chain infrastructure. The smart contract code in Kelp DAO’s bridge had been reviewed by auditors and was functioning as designed — the weakness lay entirely in the systems connecting those smart contracts to the real world.

This incident also highlights the danger of trust assumptions in cross-chain architectures. When a bridge relies on a centralized off-chain component to validate state changes, it introduces a single point of failure that undermines the security guarantees of the underlying blockchain. The crypto community must recognize that a protocol’s security is only as strong as its weakest link, and that link is increasingly found in off-chain infrastructure.

User Action Required

If you hold rsETH or any assets tied to the Kelp DAO ecosystem, monitor official channels for updates on recovery efforts and token revaluation. Consider reducing exposure to cross-chain bridge protocols that have not publicly disclosed their off-chain security measures. When evaluating any DeFi protocol, look beyond smart contract audits and assess the security of off-chain components, oracle dependencies, and administrative key management. Use hardware wallets for large holdings and maintain separate wallets for interacting with experimental or recently launched protocols. The February 2025 security landscape — with both the Bybit and Kelp DAO incidents — serves as a stark reminder that vigilance must extend to every layer of the crypto stack.

Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Always conduct your own research before making any financial decisions.

🌱 FOR BUSINESSES BitcoinsNews.com
Reach 100K+ Crypto Readers
Sponsored content, press releases, banner ads, and newsletter placements. Put your brand in front of Bitcoin's most engaged audience.

15 thoughts on “Kelp DAO Suffers $292 Million Bridge Exploit Through Off-Chain Infrastructure Attack”

  1. 292 million gone because of off-chain infrastructure, not even a smart contract bug. protocols keep ignoring anything outside the EVM and this is what happens

    1. exactly. everyone audits the smart contracts but the relayer infrastructure is just… trusted? after 2022 youd think wed learned

    2. minting rsETH without collateral means the relay validation was essentially a database write with no verification. this is not a bridge problem, its a trust architecture problem

      1. database write with no verification is generous. it was probably a single API endpoint with auth that could be spoofed. off-chain infra is where all the shortcuts live

  2. ETH at $2238 and BTC at $84373 when this hit. market was already fragile from bybit and then $292M more vanishes. bridges are the soft underbelly of defi

    1. Marcus B. market was already fragile from Bybit and Kelp DAO still had no circuit breakers. one week was apparently enough time to do nothing

  3. one week after bybit gets drained for 1.5b and kelp dao still hadnt hardened their off-chain systems. insane

    1. one week after the biggest exchange hack in history and their off chain systems were still soft. no emergency hardening, no circuit breakers. negligence at this point

      1. no circuit breakers, no rate limits on minting. after bybit the entire industry should have been on high alert. kelp dao treating their bridge like a side project

        1. circuit breakers should be mandatory for any bridge over $100M TVL. the fact that its still optional in 2025 is an industry failure not just a kelp problem

          1. off_chain_ice

            full_send_ after Bybit lost $1.5B every protocol should have implemented rate limits within 48 hours. the fact that bridges are still optional is indefensible at this point

  4. exploit_hunter

    5 stages and 3 pools means this was planned, not opportunistic. the attacker probably spent weeks mapping the relay architecture before pulling the trigger

    1. mapping relay architecture for weeks before executing is state sponsored level prep. these are not random hackers anymore, its organized infrastructure attacks

  5. 5 stage attack with counterfeit tokens across 3 pools. the sophistication keeps increasing but the root cause is always the same: insufficient input validation on critical paths

  6. off-chain relay compromise is the new attack vector and nobody is ready. every bridge audit focuses on the smart contracts but the actual signing infrastructure is running on some AWS instance with a single API key

Leave a Comment

Your email address will not be published. Required fields are marked *

BTC$62,480.00-2.6%ETH$1,687.32-3.5%SOL$68.17-4.3%BNB$572.77-2.9%XRP$1.12-3.8%ADA$0.1593-3.8%DOGE$0.0822-2.9%DOT$0.9492-2.9%AVAX$6.05-9.0%LINK$7.80-3.2%UNI$3.03-3.8%ATOM$1.81-1.0%LTC$43.44-1.4%ARB$0.0825-2.8%NEAR$2.09-6.2%FIL$0.7660-3.0%SUI$0.7041-6.0%BTC$62,480.00-2.6%ETH$1,687.32-3.5%SOL$68.17-4.3%BNB$572.77-2.9%XRP$1.12-3.8%ADA$0.1593-3.8%DOGE$0.0822-2.9%DOT$0.9492-2.9%AVAX$6.05-9.0%LINK$7.80-3.2%UNI$3.03-3.8%ATOM$1.81-1.0%LTC$43.44-1.4%ARB$0.0825-2.8%NEAR$2.09-6.2%FIL$0.7660-3.0%SUI$0.7041-6.0%
Scroll to Top