The Sandbox has halted bridging of its SAND token on Base and BNB Chain following an exploit, pulling the cross-chain routes offline as an immediate containment measure. The incident interrupts asset movement between the two networks while the team investigates. SAND is the native token of The Sandbox, a Web3 gaming and virtual-world platform where the token is used to buy virtual LAND parcels and user-created ASSETs and to cast governance votes; the franchise originated as a 2012 mobile game before developer Pixowl was acquired by Animoca Brands in 2018 and the property was rebuilt around blockchain ownership.

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. The two named networks are the specific routes taken offline: Base, the Ethereum layer-2 network launched by exchange operator Coinbase, and BNB Chain, the smart-contract blockchain tied to Binance.

In a post on X, 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. Halting a bridge is a standard containment step during an active exploit, cutting off the attack surface before further movement can occur.

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.

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 broader lesson on cross-chain risk is that 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. That exposure is well precedented across the industry: Chainalysis attributed the majority of cryptocurrency stolen in 2022 to cross-chain bridge hacks, a stretch that included the Ronin Network and Wormhole exploits, each of which resulted in losses in the hundreds of millions of dollars. Until The Sandbox publishes restart criteria, the pause remains the operative status for SAND bridging.