The Sandbox Confirms SAND Cross-Chain Bridge Vulnerability, Pauses Base and BSC Functions

iconKuCoinFlash
Share
AI summary iconSummary
The Sandbox confirmed a vulnerability in its SAND cross-chain bridge, with attackers minting uncollateralized tokens on Base and BSC. The incident, identified through on-chain data, affected less than 0.01% of the total supply. The project has paused cross-chain functions on these networks and isolated the compromised SAND tokens. Users are advised to avoid trading SAND on Base and BSC. A compensation plan is under development, with a full report to follow. The Fear & Greed Index for DeFi tokens may face short-term pressure due to such exploits.

Odaily Planet Daily reports: The Sandbox official has confirmed and contained the vulnerability exploit in the SAND cross-chain bridge, where attackers minted unbacked SAND on the Base and BSC networks, affecting less than 0.01% of the total SAND supply. SAND on Ethereum and Polygon networks remain unaffected, and user wallets were not compromised.

The Sandbox has temporarily suspended the cross-chain functionality for SAND on the Base and BSC networks, and has isolated the affected SAND tokens, which cannot currently be transferred or exchanged. The official team advises users not to trade SAND on these networks and is developing a compensation plan for affected LP users; a full incident report will be released soon.

Disclaimer: The information on this page may have been obtained from third parties and does not necessarily reflect the views or opinions of KuCoin. This content is provided for general informational purposes only, without any representation or warranty of any kind, nor shall it be construed as financial or investment advice. KuCoin shall not be liable for any errors or omissions, or for any outcomes resulting from the use of this information. Investments in digital assets can be risky. Please carefully evaluate the risks of a product and your risk tolerance based on your own financial circumstances. For more information, please refer to our Terms of Use and Risk Disclosure.