Crypto Twitter did what crypto Twitter does this weekend. Within minutes of The Sandbox disclosing a cross-chain bridge vulnerability, timelines filled with claims that attackers had minted 49 billion unbacked SAND and wiped out the project’s “entire liquidity” across two networks. The real story, based on The Sandbox’s own statement, is considerably smaller, though still worth understanding if you hold SAND or trade its liquidity pools.
What Actually Happened
On August 22, The Sandbox confirmed that its team had identified, contained, and taken control of a vulnerability in the SAND cross-chain bridge connecting Base and BNB Smart Chain. Attackers exploited the flaw to mint SAND tokens on those two networks without proper collateral backing them on the token’s home chains.According to the company’s statement, the impact affects less than 0.01% of total SAND supply. SAND on Ethereum and Polygon, where the vast majority of circulating supply and liquidity sits, was not touched. User wallets were not compromised, and holders and liquidity providers on the affected networks were told they do not need to take any personal action.The Sandbox has disabled cross-chain bridging for SAND on both Base and BSC while it completes its investigation, and it says a snapshot was taken before the incident to establish a clean baseline for any compensation owed to affected liquidity providers. A full technical post-mortem is expected once the review is complete.
Where the Alarmist Numbers Came From
The figure being thrown around, 49 billion unbacked SAND, would represent well over ten times SAND’s entire fixed 3 billion token supply cap if taken literally, which should have been the first clue something was off in how the claim was framed. Bridge exploits do sometimes produce eye-watering headline numbers because the exploited chain-side contract can mint far beyond what the home chain actually has locked, particularly on smaller networks with thinner liquidity, so a large raw minting figure on Base or BSC is plausible even while the practical damage stays contained. The company’s own framing of “less than 0.01% of supply” and “isolated” liquidity suggests that whatever was minted was quickly identified and quarantined before it could meaningfully hit the broader market.This is a useful reminder for anyone trading news off screenshots and quote-tweets rather than primary sources. A dramatic number attached to a real event travels much faster than the calmer official clarification that usually follows it.
This incident lands in a year that has already seen a string of cross-chain bridge failures, from the KelpDAO LayerZero breach in April to smaller mint exploits at Alephium and Secret Network. The mechanism is almost always the same: a bridge is supposed to only release or mint tokens on the destination chain once it verifies an equivalent amount is locked on the source chain, and when that verification step breaks, attackers can mint supply from nothing. Bridges remain, by a wide margin, the weakest link in multi-chain crypto infrastructure, and newer or secondary deployments like a token’s expansion onto additional chains tend to carry more risk than the original, more battle-tested implementation.For SAND holders, the practical takeaway is straightforward. Ethereum and Polygon positions are unaffected. If you were holding or providing liquidity for SAND specifically on Base or BSC, keep an eye on The Sandbox’s official channels for the compensation plan and the incident report, and avoid trading SAND on those two networks until bridging is restored and the situation is fully resolved.This article reflects information available as of publication and may be updated as The Sandbox releases further details.
