Verus-Ethereum Bridge Contract Hit By Suspicious $11.5M Drain

Bitbuy



A suspicious Ethereum transaction has drained roughly $11.5 million in assets from the Verus-Ethereum Bridge contract, putting another cross-chain bridge under security scrutiny.

The on-chain transaction was recorded on May 17 at 11:55:23 p.m. UTC and interacted with the Verus-Ethereum Bridge contract at 0x71518580f36FeCEFfE0721F06bA4703218cD7F63. Etherscan records show 1,625.36688649 ETH moved from the bridge contract to 0x65Cb8b128Bf6e690761044CCECA422bb239C25F9, alongside ERC-20 transfers of 103.56766017 tBTC and 147,658.836798 USDC to the same receiving wallet.

Using Etherscan’s transaction-level values, the ETH transfer was worth about $3.44 million, the tBTC transfer about $7.97 million and the USDC transfer about $147,600. That puts the total suspicious movement near $11.56 million.

The transaction is already being treated as a likely exploit by security watchers, but the technical root cause has not been confirmed. There is no verified postmortem yet explaining whether the drain involved bridge-message validation, key compromise, proof handling, contract logic, reserve accounting or another failure path.

Why The Bridge Contract Matters

The affected contract address matches the Verus-Ethereum bridge infrastructure identified in Verus materials. The Verus-Ethereum Bridge is designed to support transfers and conversions between Verus and Ethereum through the Verus Internet Protocol, with cryptographic proofs and witnesses validating notarizations created by Verus miners and stakers.

Verus describes the bridge as non-custodial and decentralized, with assets on the Ethereum smart contract secured by the Verus network. That design makes the latest drain especially sensitive because bridge systems depend on the correct handling of cross-chain verification, contract execution, liquidity reserves and settlement messages.

The asset mix also matters for recovery. ETH and tBTC can be traced on-chain, but they cannot be frozen in the same straightforward way as centralized stablecoins. The USDC portion is smaller, yet stablecoin issuer controls could become relevant if investigators or protocol teams identify freezeable balances before they are swapped or moved again.

Bridge Security Returns To The Spotlight

The Verus incident adds to a wider run of cross-chain security pressure. Recent bridge exploit coverage has already shown how quickly a single contract failure or abnormal mint can turn into user losses, while a separate THORChain exploit alert kept attention on cross-chain liquidity risks across major networks.

The post-exploit response now depends on speed and visibility. Investigators will need to track the receiving wallet, downstream swaps, exchange deposits, bridge attempts and any splitting of funds. Recent crypto seizure and freeze activity shows that public ledgers can help preserve recovery paths, but ETH-heavy exploit proceeds remain harder to contain once they are routed through decentralized liquidity or privacy infrastructure.

The next concrete updates should be an official Verus statement, bridge operating status, affected asset accounting, the exact failure path and whether any of the drained USDC can be frozen or recovered. Until then, the confirmed public record is limited but serious: one transaction moved 1,625.36 ETH, 103.56 tBTC and 147,658 USDC from the Verus-Ethereum Bridge contract to the same receiving wallet, leaving the suspected loss near $11.5 million.



Source link

fiverr

Be the first to comment

Leave a Reply

Your email address will not be published.


*