The Sandbox 2026 Base/BSC bridge-configuration exploit
Beginning around 23:41 UTC on August 21, 2026, an attacker exploited contracts associated with The Sandbox SAND bridge configuration on Base and BNB Smart Chain, enabling unbacked SAND minting without corresponding Ethereum deposits. Independent reporting based on the operator postmortem states that 14,742,341.84 SAND was drained from the Ethereum backing vault. The affected bridge paths were disabled and The Sandbox later opened a compensation process for eligible users.
Incident facts
- Incident title
- The Sandbox 2026 Base/BSC bridge-configuration exploit
- Bridge
- The Sandbox SAND Bridge
- Incident date
- 2026-08-21
- Incident type
- Exploit
- Major incident
- Yes
- Affected chains
- Ethereum, Base, BNB Chain
- Affected assets
- SAND
- Attack category
- Configuration Error
- Reported loss
- 14,742,341.84 SAND (about $697,000)
- Amount confidence
- Medium
- Loss amount basis
- Mixed Sources
- Recovery
- Unknown
- Reimbursement
- In Progress
- Restart
- Paused
- Current outcome
- Unknown
- Postmortem
- Available
- Resolution
- Unresolved
- Last reviewed
- 2026-09-09
- Last verified
- 2026-09-09
Amount and valuation
Independent coverage of The Sandbox postmortem reports 14,742,341.84 SAND drained from the Ethereum backing vault, valued at about $697,000 at the incident-period valuation.
The canonical amount is the SAND actually drained from the Ethereum backing vault. Enormous nominal unbacked-mint face values are intentionally excluded from realized loss.
14,742,341.84 SANDabout $697,000
Realized backing-vault drain, not nominal unbacked-mint face value.
Why this remains unresolved
- Final attacker-fund recovery is not established.
- The compensation process is in progress and is not recorded as completed.
- A dated unrestricted reopening of the affected Base/BSC bridge paths is not established.
Timeline events
Base/BSC bridge configuration exploited2026-08-21
An attacker exploited contracts associated with The Sandbox SAND bridge configuration on Base and BNB Smart Chain, enabling unbacked SAND minting without corresponding Ethereum deposits and draining backing assets from the Ethereum vault.
Nominal synthetic mint face values are excluded from realized loss.
Affected Base and BNB Smart Chain bridge paths disabled2026-08-22
The Sandbox disabled bridging on the affected Base and BNB Smart Chain paths during containment and warned users against trading affected SAND representations.
No unrestricted reopening is inferred.
The Sandbox publishes SAND compensation claim process2026-09-08
The Sandbox published its compensation process for users affected by the August exploit, stating that it had committed to a full compensation plan and explaining eligibility and claim mechanics.
Publication of a claim process does not establish completed reimbursement.
Evidence records
- August 22 Exploit Post-MortemThe Sandbox · Tier 1 · High reliability · primary · 2026-08-27Claim scope: Incident Case
First-party blog index exposes the August 27 postmortem summary and supports the August 21 23:41 UTC incident boundary, Base/BSC bridge-configuration vulnerability and unbacked mint without a corresponding Ethereum deposit.
- August 22 Exploit Post-MortemThe Sandbox · Tier 1 · High reliability · primary · 2026-08-27Claim scope: Event
First-party postmortem publication used for the affected bridge shutdown/containment boundary. The evidence does not establish unrestricted reopening.
- SAND Compensation: How the Claim Process WorksThe Sandbox · Tier 1 · High reliability · primary · 2026-09-08Claim scope: Reimbursement
First-party compensation-process publication. Supports in-progress reimbursement only, not completion.
- The Sandbox Retires SAND Bridge After Exploit, Plans 1:1 CompensationCrypto Payments News · Tier 2 · High reliability · secondary · 2026-08-28Claim scope: Amount
Independent postmortem-based coverage supporting 14,742,341.84 SAND / about $697,000 drained from the Ethereum vault and separating realized extraction from nominal unbacked-mint figures.
Source tiers describe evidence authority, not certainty for every claim. Tier 1 is the strongest source class; Tier 2 and Tier 3 provide progressively more secondary or supporting context. Source notes define what each record actually supports.
Known unknowns
- Final recovery amount remains unknown.
- Compensation completion remains unresolved.
- No unrestricted Base/BSC bridge reopening is established by admitted evidence.
Help maintain incident aftermath records
Support recovery, reimbursement, restart, migration, shutdown, evidence, and correction checks.
Report a correction
Report missing evidence, incorrect dates, outcome changes, recovery details, reimbursement status, or broken links. GitHub Issues are preferred for structured review; the Google Form is available if you do not use GitHub.