Sandbox halts Base and BNB Chain bridging after exploit

What happened to Sandbox bridging on Base and BNB Chain

The Web3 gaming network stopped bridging on Base and BNB Chain after an exploit hit its cross-chain infrastructure, according to CoinDesk reporting. The two named networks are the specific routes taken offline. For related coverage, see Ripple Tests XRP Trade Finance in MAS Singapore Sandbox.

The Sandbox confirmed the pause through its official channel, framing the shutdown as a response to the security incident rather than a scheduled maintenance window, in a post on X. Halting a bridge is a standard containment step during an active exploit, cutting off the attack surface before further movement can occur. For related coverage, see HTX Halts Trading for WLFI Token and USD1 Stablecoin.

Additional details on the exploit affecting SAND across Base and BSC were reported by BeInCrypto. The available evidence confirms the halt and the affected chains, but does not establish a verified figure for losses or the exact exploit vector. For related coverage, see Solana Activates 350-Millisecond Slots on Mainnet.

How the halt affects users, transfers, and risk exposure

With the bridge paused, SAND holders cannot move the token between Base and BNB Chain until the routes reopen. Deposits, withdrawals, and any in-flight transfers routed through the affected contracts are effectively frozen for the duration of the pause.

Users relying on cross-chain liquidity should wait for direct guidance from the team before attempting to bridge again, as interacting with a compromised route during an active incident carries elevated risk. A paused bridge protects funds still in custody, but it also strands assets mid-transit until a safe restart is confirmed.

Similar containment logic has played out in other recent halts, such as when MANTRA halted its chain after a Cosmos EVM module issue, where stopping activity was chosen over risking further exposure.

What the incident signals for bridge security and next steps

Bridge incidents are typically judged on containment speed, disclosure quality, and the criteria set for reopening. A halt across two named chains implies both a technical fix and an operational review before either route restarts.

Readers should watch for a post-incident disclosure detailing the exploit vector, any remediation or patching of the bridge contracts, and the conditions under which bridging resumes on Base and BNB Chain. Comparable pauses, like Aave’s decision to halt deployment across several chains, show that a staged, verification-gated reopening is the common path back to service.

The core lesson tracks with cross-chain risk broadly: bridges concentrate value and trust at a single technical chokepoint, so the response window and transparency after an exploit matter as much as the initial code. Until The Sandbox publishes restart criteria, the pause remains the operative status for SAND bridging.

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.