The 2026 DeFi Bridge Hack Wave

Cross‑chain bridges—systems that allow assets to move between blockchains—were the biggest security weak point in decentralized finance during early 2026. By mid‑May, attackers had drained about $328.6 million across eight major bridge‑related exploits, according to blockchain security trackers. The overwhelming majority of the losses came from one incident: the April 18 breach of KelpDAO’s LayerZero‑based rsETH bridge.

The attacks were different in their technical details, but they exposed the same core issue: bridges concentrate large pools of locked assets while depending on comparatively fragile verification systems and operational infrastructure.

The $292M KelpDAO–LayerZero exploit

The largest DeFi breach of 2026 occurred on April 18, when attackers drained roughly 116,500 rsETH—worth about $292 million—from KelpDAO’s cross‑chain bridge built on LayerZero infrastructure.

Investigations found that the attack did not primarily target a smart‑contract bug. Instead, it exploited weaknesses in the bridge’s verification architecture and supporting infrastructure.

Key factors included:

• Single‑verifier configuration: KelpDAO used a 1‑of‑1 Decentralized Verifier Network (DVN) setup, meaning a single verifier could approve cross‑chain messages.
• Compromised infrastructure: Attackers infiltrated RPC nodes used by the verifier system and manipulated the data used to confirm transaction validity.
• Forged cross‑chain message: The manipulated infrastructure allowed the attacker to fabricate a message indicating tokens had been burned on another chain, triggering the Ethereum contract to release funds.

LayerZero and other investigators said early indicators pointed to North Korea’s Lazarus Group—specifically the TraderTraitor cluster—as the likely actor, though attribution remains preliminary rather than legally confirmed.

The THORChain exploit

Another notable attack occurred on May 15, 2026, when the cross‑chain liquidity protocol THORChain lost about $10.8 million across multiple networks including Bitcoin, Ethereum, and BNB Chain.

Investigators believe the exploit targeted the protocol’s GG20 threshold‑signature system, which allows nodes to jointly sign transactions without revealing the full private key.

According to incident analysis, a malicious node participating in signing rounds may have gradually collected fragments of cryptographic material during legitimate operations and reconstructed the private key controlling an Asgard vault. Once the key was recovered, the attacker could sign unauthorized withdrawals.

The attack highlighted a persistent risk in cross‑chain systems that rely on distributed signing: if enough key fragments are exposed or leaked, the vault controlling bridge assets can be compromised.

The Verus–Ethereum bridge hack

On May 18, 2026, another bridge exploit drained about $11.58 million from the Verus‑Ethereum cross‑chain bridge.

The attacker extracted assets including 103.6 tBTC, 1,625 ETH, and roughly 147,000 USDC before converting them into ETH.

Security researchers found the root cause was a validation gap in the bridge logic:

• Both sides of the bridge performed checks on cross‑chain transactions.
• However, neither side required the other to confirm a crucial value—the source‑chain transfer amount.

Because that field was not strictly enforced, an attacker could submit a message that appeared valid but represented almost no real value on the originating chain, allowing the contract to release funds from reserves.

Why cross‑chain bridges keep getting hacked

The 2026 incidents reinforced a long‑standing warning in blockchain security: bridges are often the most dangerous component of DeFi infrastructure.

Several structural weaknesses repeatedly appear in bridge exploits.

1. Security concentrated in a small verifier set

Bridges often rely on a small group of validators, relayers, or verifiers to confirm cross‑chain messages. If one or more of these actors are compromised—as in the KelpDAO case—attackers can authorize fraudulent transfers.

2. Private‑key and signing‑scheme risk

Many bridges depend on multisignature or threshold‑signature systems to control vaults holding large token reserves. If attackers recover enough key fragments or compromise participating nodes, they can produce legitimate‑looking signatures for malicious withdrawals. This was a suspected factor in the THORChain exploit.

3. Incomplete message validation

Bridges must verify that events on one blockchain genuinely occurred before releasing assets on another. Missing checks or inconsistent validation rules—such as the Verus bridge’s failure to confirm source amounts—can allow forged proofs to pass verification.

4. Off‑chain infrastructure as an attack surface

Cross‑chain systems rely heavily on RPC nodes, relayers, monitoring infrastructure, and operational tooling. Compromising those systems can poison the data used by bridge verification networks, as seen in the KelpDAO exploit.

Why the attacks matter for DeFi

Bridge exploits do more than drain funds—they challenge the core promise of decentralized finance: seamless asset mobility across blockchains.

When a bridge fails:

• Wrapped assets can lose their backing
• DeFi lending markets using those assets as collateral can freeze
• Liquidity and cross‑chain trading routes can break

Because bridges act as custodial hubs that hold large token reserves, a single exploit can ripple across multiple chains and protocols.

The early‑2026 wave of attacks showed that the problem is not isolated bugs but systemic architectural risk. Until bridge designs rely on stronger verification models, more decentralized validators, and hardened operational infrastructure, cross‑chain systems will remain one of the most attractive targets in crypto security.