Nervos Network’s Force bridge hack shows why cross-chain security still matters

On June 2, 2025, security analysts reported that Nervos Network’s Force cross-chain bridge had been attacked and that about $3 million in crypto was lost. The reported assets included ETH, stablecoins, and wrapped BTC, which matters because bridges are built to move value across chains and therefore concentrate both liquidity and attack surface.

What happened, and why does it matter?

The immediate issue was not just the size of the loss. It was the type of system involved. Cross-chain bridges are useful because they connect otherwise fragmented blockchain ecosystems, but they also create a point where a failure can affect multiple asset types at once. In the reporting from The Block, the loss was described as an apparent DeFi hack, which is consistent with the long-running pattern that bridge incidents can be both technically complex and operationally disruptive.

Who is affected by a bridge breach like this?

The first group affected is usually bridge users who may face direct asset loss or delayed access to funds. The second is the protocol team, which has to assess whether the issue is isolated, whether related contracts or routes are exposed, and whether the bridge should remain available while the review is underway. A third group is any business that depends on bridge liquidity for treasury movement, settlement, or trading operations, because even a single incident can change routing assumptions quickly.

What are the limitations and failure modes?

One clear limitation is that bridge security depends on more than the transfer interface itself. If a bridge is targeted, the practical response is to verify which assets and routes are affected, pause or restrict exposure where possible, and coordinate a clear status update for users and counterparties. Binance’s reporting also shows that market reaction can be immediate, so operators need monitoring that covers both technical integrity and price or liquidity stress, not just smart contract health.

What should operators do now?

Operators that move funds across chains should treat bridge selection as a risk decision, not a convenience choice. That means checking whether a route has been stressed before, limiting balances held in transit, and defining what happens if a bridge becomes unavailable. For payment and treasury teams, the practical goal is to reduce dependency on any single transfer path and to keep reconciliation procedures ready if a route is interrupted.

For businesses handling crypto payments, the lesson is straightforward: security and operational controls matter as much as speed. Radom’s crypto payments stack is built around that broader operational reality, but the wider point applies across the market. If a bridge is part of your flow, it should be treated as a monitored dependency, not a background utility.

Why this still matters now

This was a June 2025 event, but the relevance has not faded. Bridge attacks remain a recurring category of crypto loss because they exploit systems designed to move value across fragmented networks. The operational takeaway is to keep controls current, assume that routing can change under stress, and review whether your payment or treasury process can still function if a bridge is compromised or taken offline.

FAQ: Was the loss confirmed by more than one source? Yes. The Block reported the roughly $3 million loss, and Binance Square also described the Force Bridge attack on the same date. Does this mean all bridges are unsafe? No, but it does mean they should be evaluated with the same discipline used for other high-value financial infrastructure.