Verus Ethereum Bridge Forged Transfer Exploit Drains $11.5M

The Verus Ethereum bridge forged transfer exploit of 2026 struck on May 18, draining more than $11.5 million in crypto assets after an attacker fed a fraudulent cross-chain message directly to the bridge contract. Security firms Blockaid, PeckShield, GoPlus Security, and ExVul each confirmed details of the breach, painting a picture of a validation gap that let fake instructions pass through the protocol’s verification layer and trigger three separate reserve transfers into a drainer wallet.

Inside the Verus Ethereum Bridge Forged Transfer Exploit

The attacker started small. Hours before the main strike, the wallet identified as 0x5aBb…D5777 received 1 ETH through crypto mixer Tornado Cash, a funding move that security researchers often see before deliberate protocol attacks, since it masks the transaction trail leading back to the perpetrator.

Once funded, the attacker sent a low-value test transaction to the bridge contract. GoPlus Security explained that this initial probe was followed by a function call that triggered a batch transfer of reserve assets out of the bridge and into the drainer wallet. The stolen pool included 103.6 tBTC, 1,625 ETH, and nearly 147,000 USDC, according to PeckShield data. The attacker then swapped those mixed assets into 5,402 ETH worth roughly $11.4 million at prices current at the time.

ExVul described the core mechanism as a ‘forged cross-chain import payload’ that cleared the bridge’s own verification checks without challenge. Three separate outbound transfers followed, each moving reserve funds directly into the attacker-controlled address labeled 0x65C…C25F9. The bridge did not pause. No emergency circuit breaker triggered. The funds simply left.

What Was the Root Cause of the Verus Exploit?

Blockaid identified the root cause: a missing source-amount validation inside the checkCCEValues function of the Verus-Ethereum bridge smart contracts. The firm explicitly ruled out an ECDSA bypass, a notary key compromise, and a parser bug. The contract simply never checked whether the value claimed in an incoming cross-chain message matched the value authorized to move.

Blockaid said fixing that specific gap would require around 10 lines of Solidity code. That is a number worth sitting with for a moment. A protocol holding tens of millions of dollars in bridge reserves was undone by a validation step that fits inside a short function. GoPlus Security reached a parallel conclusion, calling the failure ‘highly likely’ tied to cross-chain message validation failure, withdrawal logic bypass, or an access control weakness, all flavors of the same underlying problem.

ExVul added a practical recommendation: cross-chain proof systems should require that transfer execution be tied directly to authenticated payload data before any funds move. A forged payload should not be able to authorize even a penny of outbound transfer, let alone millions.

The exploit was not an ECDSA bypass, not a notary key compromise, and not a parser/hash-binding bug, it was a missing source-amount validation in checkCCEValues, fixable with around 10 lines of Solidity code.

Verus Bridge Exploit Mirrors 2022 Nomad and Wormhole Attacks

Blockaid said the incident looked a lot like the 2022 Nomad Bridge exploit and the Wormhole exploit, two attacks that remain among the most studied bridge failures in crypto history. In both cases, fraudulent transfer instructions tricked protocols into releasing reserve assets they were never authorized to release. The Verus incident follows the same pattern: craft a message that looks valid, push it through a verification layer that does not check the right variables, and collect the proceeds.

The Verus-Ethereum bridge launched in 2023 and is designed to let users move and convert assets between the Verus network and Ethereum. The Verus protocol itself dates to 2018 and runs on a hybrid proof-of-work and proof-of-stake consensus model. As of publication time, the Verus team had not released a public statement about the exploit, which security researchers noted is unusual given the scale of the loss.

The silence from the core team is the kind of gap that makes an already-bad situation worse for users trying to decide whether to keep funds on the protocol. Cross-chain bridges are high-value targets precisely because they concentrate large reserves in contracts that must accept and execute messages from external chains, and those messages are only as safe as the validation logic that screens them.

Is DeFi Bridge Security Getting Worse in 2026?

The Verus loss is not an isolated incident. Crypto hackers stole more than $168.6 million from 34 DeFi protocols during the first quarter of 2026 alone, according to security tracking data from DefiLlama. April then stacked on two of the year’s largest single attacks: the reported $280 million Drift Protocol exploit and the $292 million Kelp exploit. The weekend that the Verus bridge was drained also saw cross-chain liquidity protocol THORChain confirm a separate $10 million exploit.

The pattern across these attacks is consistent. Bridge and interoperability infrastructure carries some of the highest concentration of risk in DeFi. Each bridge is essentially a message-passing system that holds real collateral, and any flaw in how that system validates incoming messages is a direct path to draining those reserves. The Verus exploit, the THORChain breach, Nomad in 2022, Wormhole in 2022, the attack surface has not changed much. What changes is the dollar value sitting inside these contracts.

ExVul’s post-mortem recommendations are worth taking seriously across the sector: stricter payload validation, layered verification protections, and emergency pause mechanisms that can halt unusual outbound transfers before they complete. None of those are exotic engineering challenges. They are standard defensive measures that, had they been in place on the Verus bridge, would have stopped this specific attacker cold.

The harder question is why protocols keep launching bridges without them. The Verus team built a two-chain bridge that held over eleven million dollars in user assets, apparently without a circuit breaker or a validation step on outbound transfer values. That is not bad luck. That is a design choice, and the users who deposited tBTC, ETH, and USDC into those reserves are the ones paying for it.

• Stricter payload validation on incoming cross-chain messages
• Layered verification checks before any reserve transfer executes
• Emergency pause mechanisms triggered by unusual outbound transfer volume
• Direct binding between transfer execution and authenticated payload data

This article is for informational purposes only and does not constitute investment advice. Every investment and trading decision involves risk. Readers should conduct their own research before making any financial decisions.