The Sandbox reports security incident impacting cross-chain bridging infrastructure. August 24, 2026 @ 3:44 pm By Omar Faridi The Sandbox, the blockchain-based metaverse and gaming platform, faced a significant security incident involving its cross-chain bridging infrastructure. The vulnerability allowed an unauthorized party to generate large volumes of SAND tokens without proper collateral on the Base and BNB Smart Chain networks. Security researchers first detected unusual activity around August 21-22, 2026. Firms such as Blockaid and PeckShield reported that an attacker had compromised permissions tied to the project's LayerZero-based Omnichain Fungible Token (OFT) setup. By exploiting a function known as approveAndCall, the actor gained the ability to create tokens on the secondary chains without corresponding locked SAND on Ethereum. The Sandbox team has identified and fully contained a recent vulnerability regarding the SAND cross-chain bridge on Base and BNB Smart Chain (BSC). The impact is minimal, representing less than 0.01% of the total SAND token supply. SAND tokens on Ethereum and Polygon are NOT... - The Sandbox (@TheSandboxGame) August 22, 2026 Early alerts noted hundreds of millions of tokens appearing, with subsequent tallies showing roughly 14.9 billion SAND directed to a pair of addresses linked to the activity. Broader estimates placed the face-value total of newly created tokens in the tens of billions of dollars across hundreds of transactions. Some analyses even described far higher nominal figures distributed over multiple addresses during a multi-hour window. Despite the scale of the unauthorized minting, the real-world financial impact remained limited. Investigators determined that only about 14.75 million legitimately backed SAND - valued at approximately $675,000 at the time - left the Ethereum-side bridge adapter, along with a modest amount of ETH. The Sandbox itself assessed the overall effect at less than 0.01 percent of the token's legitimate maximum supply of 3 billion. The project responded swiftly. Officials confirmed they had identified and fully contained the issue. Bridging functions to and from Base and BNB Smart Chain were disabled, effectively isolating the unbacked tokens so they could not be moved or redeemed against the Ethereum collateral. SAND held on Ethereum and Polygon remained completely unaffected. No individual user wallets were compromised, and the SAND locked on Ethereum that underpins all bridged tokens stayed secure. Major exchanges reacted cautiously. South Korean platforms Upbit and Bithumb suspended SAND deposits and withdrawals. Users were strongly advised not to buy, sell, or trade the token on the affected networks while liquidity there remained compromised. The Sandbox said it captured a pre-incident snapshot of balances and is preparing a compensation framework for eligible liquidity providers affected by the event. The team pledged to release a full technical post-mortem once its investigation concludes. Community members affected by liquidity pool disruptions were directed to contact official support channels. The episode underscores ongoing challenges with cross-chain bridges and omnichain token designs in the broader cryptocurrency ecosystem. While the rapid isolation of the affected networks prevented wider damage, it also highlighted how permission and delegate mechanisms can become points of failure. For SAND holders on the primary chains, the incident appears to have been successfully limited, with core infrastructure and user assets preserved. This event serves as another reminder of the importance of security reviews for multi-chain deployments as blockchain projects continue expanding their interoperability features. Sponsored Links by DQ Promote

Sandbox bridge exploit mints 14.9B unbacked SAND on Base and BSC. 2026-08-23 04:37:57 Key takeaways. * The Sandbox suffered a bridge exploit on August 21 that minted 14.9 billion unbacked SAND tokens on Base and BSC networks. * Peckshield identified 14.9 billion unbacked SAND tokens, nearly five times larger than SAND's 3 billion legitimate total supply. * The Sandbox disabled bridging immediately after detection and plans compensation for affected liquidity providers before restoring bridges. The Sandbox, the metaverse gaming platform behind the SAND token, contained a bridge exploit on August 21 that minted approximately 14.9 billion unbacked SAND tokens across Base and BNB Smart Chain (BSC) networks. The attacker exploited vulnerabilities in the bridges' minting mechanism, creating tokens without real backing on both networks. The Sandbox disabled bridging on Base and BSC immediately after detection, preventing further unauthorized token movement. Bridge exploits have topped $320 million in losses across the crypto industry over the first half of the year, with attackers increasingly targeting smart contracts that connect separate blockchains. Attacker exploits Base and BSC bridge minting mechanism. The Sandbox contained a vulnerability affecting its cross-chain bridges on Base and BNB Smart Chain (BSC). An attacker exploited the bridges' minting mechanism to create SAND tokens with no real backing on both networks. The Sandbox disabled bridging on Base and BSC as soon as the exploit was detected, cutting off the attacker's ability to move the fabricated tokens further. The Sandbox's bridge infrastructure normally works by locking SAND on one chain, typically Ethereum, and minting an equivalent, fully backed amount on the destination network. That 1:1 backing model broke down in this incident, allowing tokens to be minted on Base and BSC without a matching lock on the source chain. The Sandbox said the incident affected less than 0.01% of SAND's total supply in terms of genuine backing at risk. SAND held on Ethereum and Polygon, user wallets across the ecosystem, and the Ethereum-locked assets that back the token remained untouched throughout the exploit, the company said. Peckshield identifies 14.9 billion unbacked SAND across two addresses. Peckshield identified approximately 14.9 billion unbacked SAND minted across two addresses tied to the exploit. The scale of that figure stands out given SAND's legitimate total supply is capped at 3 billion tokens, meaning the minted amount was nearly five times larger than every real SAND token that has ever existed or will exist. The mismatch is common in bridge exploits, where an attacker manipulates a smart contract's mint function rather than actually stealing locked collateral. Similar mint-based attacks have hit other protocols throughout the year, including a bridge exploit that let an attacker mint 1 billion unauthorized DOT tokens on Polkadot's bridge earlier in the year, and a smaller incident where roughly 13.76 million unbacked ALPH tokens were created on the Alephium bridge. The platform is preparing a compensation plan for eligible liquidity providers who held positions affected by the unbacked minting, and it has advised users not to trade SAND on Base or BSC until the bridges are restored. Bridge exploits top $320 million in industry losses. Bridge exploits have topped $320 million in losses across the crypto industry over the first half of the year, as attackers have increasingly started targeting the smart contracts that connect separate blockchains rather than individual protocols. The pattern includes the Gravity Bridge exploit that saw a hacker drain $5.4 million and route the funds through Binance before the trail went cold. The next step for The Sandbox is a post-mortem on how the bridge's minting controls failed and a security audit before Base and BSC bridging is switched back on. Coinbase plans to delist SAND futures on August 26. SAND was trading near $0.039 as of this week. Coinbase announced its plans to delist ten perpetual futures contracts, including SAND, effective August 26, as part of a broader review of trading volume and liquidity across its derivatives markets. Open positions will be settled automatically at that point. Faq. What happened in The Sandbox bridge exploit on August 21? An attacker exploited vulnerabilities in The Sandbox's cross-chain bridges on Base and BNB Smart Chain (BSC) to mint approximately 14.9 billion unbacked SAND tokens across two addresses. The Sandbox disabled bridging on Base and BSC immediately after detection to prevent further unauthorized token movement. How much SAND was minted compared to the legitimate total supply? Peckshield identified approximately 14.9 billion unbacked SAND minted in the exploit. SAND's legitimate total supply is capped at 3 billion tokens, meaning the minted amount was nearly five times larger than every real SAND token that has ever existed or will exist. When will Coinbase delist SAND futures contracts? Coinbase announced its plans to delist ten perpetual futures contracts, including SAND, effective August 26, as part of a broader review of trading volume and liquidity across its derivatives markets. Open positions will be settled automatically at that point. Disclaimer: The information on this page may come from third-party sources and is for reference only. It does not represent the views or opinions of Gate and does not constitute any financial, investment, or legal advice. Virtual asset trading involves high risk. Please do not rely solely on the information on this page when making decisions. For details, see the Disclaimer.

Sandbox's bridge freeze raises red flags: is Web3 gaming's bridge dependency a ticking time bomb? An exploit on Base and BNB chains forced an abrupt halt, but sources close to the situation point to systemic weaknesses the industry keeps sweeping under the rug. Finn Calloway Investigative Reporter · CCN I'm sitting here sifting through the aftermath of The Sandbox's decision to sever bridging to Base and BNB Chain, and one question keeps nagging at me: why does this keep happening in an industry that claims to have learned from every prior disaster? The move came right after an exploit hit those chains, yet the official line is thin on details about what exactly got drained or how much user funds sit in limbo. Sources close to the situation tell me the pause wasn't just precautionary - it was a scramble to contain damage that could have spread further if left unchecked. What they're not telling you is that The Sandbox's reliance on these external bridges has always been a calculated risk dressed up as innovation. Mainstream coverage treats this as an isolated incident, but let's be real: Web3 gaming titles like The Sandbox have funneled millions through cross-chain pathways without the kind of rigorous audits that traditional finance demands. I've seen internal chatter suggesting the exploit exploited a known vector in how assets move between Ethereum layers and BNB's ecosystem, yet no one at the company has stepped up with a timeline for restoring service. "What they're not telling you is that this exploit might just be the tip of the iceberg in an ecosystem built on shaky code and unchecked bridges." Dig deeper and the numbers tell a story the press release skips. The Sandbox ecosystem reportedly handles over $50 million in weekly bridge volume at peak times, much of it tied to user-generated land and asset trades. When those flows stopped cold, it wasn't just gamers left hanging - developers and liquidity providers who built entire strategies around seamless cross-chain movement now face sudden illiquidity. My contacts indicate the exploit targeted a vulnerability in the bridging contracts themselves, not some rogue wallet, which raises the hard question of why such a critical piece of infrastructure wasn't hardened after similar attacks elsewhere. This isn't the first time a gaming project has hit the brakes on bridges, and pretending otherwise ignores the pattern. Look at the broader landscape: other Web3 titles have quietly paused similar functions after exploits, only to resume without addressing root causes like centralized control points or unpatched smart contracts. What The Sandbox isn't disclosing publicly is whether this halt reveals overexposure to chains with their own security track records - BNB has faced scrutiny before, and Base is still maturing. Investors pouring capital into metaverse plays need to ask why these projects treat bridging as plug-and-play rather than a high-stakes engineering challenge. From my vantage point, the real story lies in the incentive misalignment. Gaming networks chase user growth and token utility by promising frictionless movement of assets, yet they outsource the security of those movements to third-party bridges that often lack the transparency of the games themselves. Sources close to the situation whisper that The Sandbox's team knew bridging risks were mounting but prioritized feature rollouts over stress-testing. That approach might boost short-term metrics, but it leaves everyday participants holding the bag when an exploit lands. Regulators and institutional players watching from the sidelines should take note too. If a prominent Web3 gaming network can flip the switch on bridging without warning, what does that say about the supposed decentralization these projects market so heavily? The exploit and subsequent pause expose how dependent the space remains on a handful of chains and their infrastructure, creating single points of failure that no amount of hype can disguise. I've yet to hear a convincing answer on what safeguards will prevent a repeat when volumes scale again. Ultimately, this episode forces a reckoning the industry has dodged for too long. The Sandbox's bridge stoppage isn't just a technical hiccup - it's a warning that Web3 gaming's growth narrative rests on fragile foundations. Until projects prioritize verifiable security over rapid expansion, expect more abrupt halts and the same vague assurances that follow. My sources suggest the fix could take weeks, not days, which means the clock is ticking on user trust. Finn Calloway. Investigative Reporter Finn has been covering crypto scandals and back-room deals since 2018. Nothing surprises him anymore. Based on reporting from CoinDesk: Bitcoin, Ethereum, Crypto News and Price Data. Original analysis and reporting by CCN.