Exchange Ranking
Top Exchanges
24h Volume Ranking
Popularity Ranking
Exchange BTC Balance
Proof of Reserves
Decentralized Exchanges
Funding Rate
Funding Heatmap
Liquidation Data
Max Pain
Long/Short Ratio
Whale L/S Ratio
Binance/Okex/Huobi L/S
Bitfinex Margin L/S
ETF Tracker
Solana ETF
XRP ETF
Hong Kong ETF
Bitcoin Treasuries
Crypto Reversal
Ethereum Reserves
HyperLiquid Wallet Analysis
Hyperliquid Whale Watch
Large Transactions
On-chain Movement
Bitcoin ROI
Stablecoin Market Cap
Options Analysis
News
Articles
Economic Calendar
Features
Wallet
Contract Calculator
Security
Collections
Watchlist
Following
BTC 
ETH Ethereum bridge protocols were stolen one after another, resulting in a total loss of US$31.7 million.
It was reported that two Ethereum bridge protocols lost a total of US$31.7 million in a few hours, and a third protocol suspended its pledge function during the same period. This series of incidents has reignited a review of the safety of cross-chain bridges. Currently, independent verification of attack methods and affected assets remains limited.
According to relevant reports, these losses were part of a series of attacks on Bitcoin and Ethereum-related protocols within hours. The core of the event focuses on the Ethereum infrastructure, rather than the price fluctuations of any single token. Bridging protocols transfer assets between different blockchains and gather a large pool of funds, making them repeatedly targets of high-value attacks.
In addition to two bridging events, another protocol suspended the pledge function for the same period of time. The pledge suspension is a defensive measure commonly used to control risk or prevent further capital outflows during team investigations, although the report did not elaborate on the specific reasons for the agreement.
Confirmed and unverified information
The $31.7 million bridging loss mentioned in the report originated from early breaking news, but the research behind this article has only been partially verified. There is currently no independently confirmed on-chain data, transaction hashes or attacker identity information. Key details remain unclear: the specific attack modus operandi for each bridging protocol, the exact type of stolen assets, and the complete protocol-level response have not been independently confirmed. Readers should regard the total loss as report data to be confirmed, and ultimately need to wait for confirmation by the blockchain browser or official post-mortem analysis report.
Security monitoring accounts have flagged these incidents on the X platform, but the specific content of those posts is not reproduced in this article because their exact wording and technical details cannot be verified. The situation may become clearer as affected teams issue incident reports.
What bridging risks mean to Ethereum users
The consequences of bridging attacks go far beyond the direct impact on victims. When cross-chain infrastructure fails, users of individual DeFi applications using the same infrastructure often withdraw funds, tightening liquidity and exposing all agreements that rely on the same track to more cautious scrutiny. The almost simultaneous occurrence of the two losses is the most eye-catching aspect. Concentrated outbreaks of similar events amplify uncertainty more than isolated incidents, which is why the third agreement decided to suspend pledges-which is more like a risk management signal than a routine maintenance step.
Bridge and repeater issues are not the first time in recent months. Similar defensive suspensions have occurred after other incidents, such as the bridge closure after a Solana attack resulted in $1.65 million in damage, and the loss of a cross-chain protocol Solana repeater, which highlight the speed at which operators are now taking to control the damage. At present, actual enlightenment is more operational than speculative. Users who interact with bridges associated with the affected protocol should probably wait for official confirmation and audit before assuming that service is normal. The full scope of these events will not be clear until verifiable on-chain data is released.
