The Verus-Ethereum bridge lost $11.58 million in a few hours on May 18. The vulnerability was the same source-destination value gap that killed Wormhole in February 2022 and Nomad in August 2022. For asset recovery teams advising clients in bridge-exposed positions, the next exploit of this class should be a working assumption. The response playbook is worth assembling before it lands, with VASP relationships and freeze templates already in place.
What happened
Just after 00:54 GMT on May 18, 2026, security firm Blockaid flagged suspicious activity on the Verus-Ethereum bridge contract. The attacker had already drained 1,625 ETH, 103.6 tBTC, and 147,000 USDC. Within hours, those assets were consolidated into roughly 5,402 ETH, worth about $11.4 million at the time, and parked in a flagged wallet that is still on-chain.
Tornado Cash funded the attacker wallet with 1 ETH approximately 14 hours before the first malicious transaction. That timing is consistent with deliberate operational preparation by an actor who knew which contract function they were going to call.
Verus issued a public statement confirming the exploit on May 18 and acknowledged the funds remained traceable. The team paused bridge operations and began coordinating with security partners. As of disclosure, the stolen ETH had not been moved to a second mixer.
The forensic angle
The Verus bridge let users move VRSC and related assets between the Verus chain and Ethereum. To do that safely, a bridge has to enforce one invariant above all others: the value released on the destination chain must equal the value locked or burned on the source chain. The Verus implementation didn’t verify that match. The contract released assets on the Ethereum side without confirming the corresponding backing on the Verus side. That single missing check is the entire exploit.
This is the same class of vulnerability that drained Wormhole of $325 million in February 2022 (where the bridge accepted forged guardian signatures) and Nomad of $190 million in August 2022 (where the contract treated unverified messages as valid). The specific implementation details differ, but the underlying failure is identical: the bridge released value on one side without proving it was backed on the other.
For forensic teams, that classification matters. When you can place an exploit inside a known vulnerability class, you can predict the attacker’s post-drain behavior with high confidence. In every bridge exploit of this class, the attacker has done the same three things: consolidate stolen tokens into ETH or stables, sit on the funds while monitoring law enforcement attention, and then begin a slow off-ramp through mixers, cross-chain bridges, or peer-to-peer markets.
The Verus attacker has already completed step one and is currently in step two. The off-ramp hasn’t started. That’s the recovery window.
Who this hits
The direct loss landed on Verus liquidity providers and on any user holding wrapped Verus assets on Ethereum at the time of the drain. Indirectly, it hits every law firm and recovery practice that has clients exposed to second-tier cross-chain infrastructure. A retail user holding bridged VRSC didn’t choose this protocol because they read the audit reports. They chose it because their wallet or DEX aggregator offered it as a path.
The lawyers picking up these cases now face a familiar problem: a client with on-chain proof of loss, a known attacker wallet, traceable funds that are about to disappear into mixers, and a narrow window in which freezes at VASP off-ramps are still viable.
What it means for recovery teams
Three things matter for the work over the next two to six weeks.
First, attribution is downstream of bridge classification. The Tornado Cash funding signature, the consolidation into ETH, the patience between drain and off-ramp – these are all consistent with the documented behavior of professional actors who recycle infrastructure across bridge exploits. Asset recovery counsel can build a parallel attribution case using public on-chain forensics, prior matched signatures, and TRM or Chainalysis cluster data, without waiting for a formal DPRK or organized-crime designation. This matters for both freeze requests and any later civil claim.
Second, the freeze window is operational work. Once the attacker begins moving funds, the speed of the recovery is determined by how quickly counsel can issue freeze requests to VASPs across multiple jurisdictions. That depends on having pre-existing relationships and standardized request formats ready before the off-ramp starts. Recoveris’s Aftercare Protocol exists precisely to compress this window, delivering initial tracing inside 24 hours and executing freeze requests directly across a 150+ VASP partner ecosystem. The window closes in hours once funds start moving.
Third, the lesson generalizes. Bridges with source-destination value verification gaps tend to fail repeatedly across the industry. Wormhole, Nomad, Ronin, Multichain, Orbit Chain, and now Verus all share variations of this defect. For clients exposed to second-tier bridges, the next exploit of this class should be a working assumption. The response playbook is worth assembling before it lands, with legal templates and VASP relationships already in place.
For lawyers building books in asset recovery, the Verus case is worth keeping as a template. The vulnerability is documented, the attacker’s pattern is predictable, and the recovery window is measurable. When the next bridge of this type fails, the playbook will already exist.
Sources
- Ongoing exploit drains $11.6 million from Verus-Ethereum bridge: Blockaid – The Block
- Verus-Ethereum bridge loses $11 million as hackers keep targeting cross-chain infrastructure – CoinDesk
- $11.58M Drained in Ongoing Exploit on Verus-Ethereum Bridge – The Defiant
- Flagged Live: Attacker Flips $11.5M in Stolen Verus Assets to ETH Following Tornado Cash Setup – Bitcoin.com News
- Crypto Bridge Exploits Hit $328.6M in May as PeckShield Tracks 8 Major Incidents – Bitcoin.com News
- Bridge hacks back in vogue as Verus exploit brings 2026 total to $329M – Protos
If your platform or users have been affected by recent exploits, immediate forensic intervention is critical to tracing and freezing assets before they reach obfuscation services.
