April 22, 2026 ChainGPT

$292M KelpDAO Hack Shows Why Cross-Chain Bridges Are Crypto’s Achilles’ Heel

$292M KelpDAO Hack Shows Why Cross-Chain Bridges Are Crypto’s Achilles’ Heel
Headline: $292M KelpDAO Hack Highlights Why Bridges Remain Crypto’s Achilles’ Heel A recent $292 million exploit tied to KelpDAO has once again exposed a persistent weakness in decentralized finance: cross-chain bridges. The attack — which targeted KelpDAO’s implementation of LayerZero’s cross-chain messaging infrastructure — is the latest in a string of bridge-related hacks that have siphoned billions from the crypto ecosystem, underscoring why bridges are repeatedly among the easiest points of failure. How bridges are supposed to work — and why they don’t Bridges let users move tokens between blockchains (for example, sending assets from Ethereum to another network). Conceptually, the destination chain needs proof that the tokens were locked on the source chain before minting an equivalent “wrapped” token (like rsETH or WBTC). In a perfect world, the destination chain would independently verify the lock. In practice, full verification is often too expensive or complex. “Most bridges don’t fully verify what happened on another chain,” Ben Fisch, CEO of Espresso Systems, explains. Instead, they outsource that verification to a smaller system — validator groups or third-party messaging protocols such as LayerZero or Axelar. That outsourced component becomes the single source of truth, and therefore a single point of failure. What happened in the KelpDAO incident According to experts, attackers compromised nodes that feed data into the cross-chain messaging layer and supplied a false “version of reality.” “The bridge worked as designed. It just believed the wrong information,” Fisch said. In other words, the exploit didn’t necessarily break the bridge’s logic — it subverted the inputs it relied on, allowing attackers to mint or move assets that weren’t actually backed on the original chain. Bridge hacks can look different at the surface — stolen keys, buggy smart contracts, social-engineering attacks — but those are often symptoms of a deeper architectural problem. “You see code vulnerabilities, centralization issues, social engineering, even economic attacks. Usually it’s a mix,” said Sergej Kunz, co-founder of 1inch. Why the problem persists Several forces keep bridges fragile: - Short-term incentives: Projects prioritize fast launches, user growth and TVL over long, costly security builds. “Security is often not the top priority,” Kunz said. - Resource constraints: Robust auditing, continuous monitoring and secure infrastructure cost time and money that many teams lack. - Composability and complexity: Each additional chain integration multiplies assumptions and attack surfaces. “Every new connection adds more assumptions,” Fisch noted. - Contagion: Bridged assets are used across DeFi — lending platforms, liquidity pools, yield strategies — so a compromised asset can infect unrelated protocols that treat the bridged token as legitimate. How to make bridges safer Experts point to several mitigation strategies that could reduce risk: - Eliminate single points of failure by using independent, diverse data sources rather than a single shared provider. - Harden infrastructure with hardware protections and improved monitoring to detect misconfigurations early. - Move toward cryptographic verification where possible — designs that validate cross-chain state without trusting intermediaries. - Avoid overreliance on validator-based bridges; as Kunz puts it, “As long as we rely on validator-based bridges, these problems will continue.” But there’s no silver bullet. Fisch warns that if many systems rely on the same underlying services, a single compromise can ripple across the ecosystem: “If everyone is relying on the same source, you haven’t reduced risk. You’ve just copied it.” Takeaway The KelpDAO-related $292 million exploit is another reminder that cross-chain infrastructure remains one of crypto’s biggest unresolved security challenges. Fixing it will require coordinated engineering effort, better incentives for robust security, and a move away from brittle, centralized trust assumptions — otherwise, bridges will keep being the most attractive target for attackers. Read more AI-generated news on: undefined/news