Two Ethereum bridges reportedly lost a combined $31.7 million within hours of each other, while a third protocol halted staking during the same period, creating a cluster of incidents that has renewed attention on cross-chain bridge security. Independent confirmation of the exploit methods, affected assets, and full protocol responses remains limited.

The losses were part of a series of attacks on Bitcoin- and Ethereum-linked protocols that occurred hours apart, totaling roughly $35 million, according to CoinDesk reporting. The incidents focused on Ethereum infrastructure rather than the price movement of any individual token.

The bridge failures fit a broader pattern of recent cross-chain incidents, including the Verus Ethereum bridge exploit, which drained $7.54 million in what was described as a second breach since May. Bridges are designed to move assets between blockchains, but they often hold large pools of locked funds and have repeatedly become high-value targets. Cross-chain bridges have accounted for several of the largest exploits in crypto history, including the Ronin Network breach that resulted in roughly $625 million in losses in March 2022 and the Wormhole bridge exploit that led to approximately $320 million in losses the month prior. These incidents prompted industry-wide calls for improved bridge auditing, multi-signature controls, and real-time monitoring systems—measures that remain unevenly adopted across the ecosystem.

In addition to the two bridge incidents, a separate protocol paused staking during the same stretch. A staking halt is commonly used as a defensive measure to contain risk or prevent additional outflows while a team investigates. However, the available brief does not provide the specific reasoning behind this protocol's decision.

What has been confirmed and what remains unclear

The reported $31.7 million figure for the bridge losses comes from early breaking-news coverage, and the underlying details remain only partially verified. At this stage, there are no independently confirmed on-chain totals, transaction hashes, or attacker identities available in the source material.

Several key points remain unresolved, including the exploit method used against each bridge, the exact assets taken, and the full scope of each protocol's response. The reported loss total should therefore be treated as preliminary until it is confirmed through block explorers, official team statements, or post-mortem reports.

Security monitors on X flagged the incidents as they emerged, but specific claims from those posts are not reproduced here because the exact wording and technical breakdowns could not be independently verified from the available material. More precise information may become available if the affected teams publish incident reports.

Why bridge risk matters for Ethereum users

Bridge exploits can affect more than the protocols directly targeted. When cross-chain infrastructure fails, users across connected DeFi applications may reassess exposure, liquidity can tighten, and protocols relying on the same infrastructure can face increased scrutiny. The interconnected nature of bridge architecture means that a single failure can produce cascading effects across lending markets, decentralized exchanges, and yield platforms that depend on wrapped or bridged versions of assets for liquidity.

The near-simultaneous timing of the two reported bridge losses is the most notable aspect of the episode. Clustered incidents can increase uncertainty more quickly than isolated failures, which is why the third protocol's decision to halt staking appears to be a risk-management step rather than routine maintenance, based on the information currently available.

The incidents also follow other recent bridge and relayer disruptions. Similar defensive actions were taken after the Allbridge Core shutdown following a $1.65 million Solana exploit and after an Across Protocol Solana relayer loss, illustrating how quickly operators may move to limit damage when infrastructure risk emerges.

For now, the situation remains operational rather than speculative. Users interacting with bridges tied to the affected protocols may wait for official confirmations, audits, or post-mortems before assuming normal service has resumed. The full scope of the incidents will depend on verifiable on-chain data and formal disclosures from the teams involved.

Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. Cryptocurrency and digital asset markets carry significant risk. Always do your own research before making decisions.