BSC Token Hub 2022 forged-proof exploit
In October 2022, an attacker exploited BSC Token Hub by forging a bridge proof, creating and taking two million BNB. The nominal value was nearly $570 million, while BNB Chain later stated that about $100 million remained unrecovered after validators paused and resumed the network.
Incident facts
- Incident title
- BSC Token Hub 2022 forged-proof exploit
- Bridge
- BSC Token Hub
- Incident date
- 2022-10-06
- Incident type
- Exploit
- Major incident
- Yes
- Affected chains
- BNB Beacon Chain, BNB Chain
- Affected assets
- BNB
- Attack category
- Message Verification Failure
- Reported loss
- Nearly $570 million minted; about $100 million unrecovered
- Amount confidence
- High
- Loss amount basis
- Nominal Minted Value Separated From Estimated Unrecovered Amount
- Recovery
- Partial Recovery
- Reimbursement
- Not Applicable
- Restart
- Reopened
- Current outcome
- Deprecated After Incident
- Postmortem
- Partial
- Resolution
- Unresolved
- Last reviewed
- 2026-07-28
- Last verified
- 2026-07-28
Amount and valuation
Two million BNB were minted and taken, valued near $570 million; BNB Chain reported about $100 million moved off-chain and remained unrecovered.
The $570 million figure describes the nominal value of two million BNB created and taken. The approximately $100 million figure describes the amount BNB Chain said remained unrecovered after the coordinated response.
2,000,000 BNB minted and takennearly $570 million
Nominal amount created through the forged-proof exploit.
about $100 million moved off-chain and remained unrecoveredabout $100 million
Estimated unrecovered amount, distinct from the nominal minted value.
Why this remains unresolved
- The final disposition of the approximately $100 million described as unrecovered is not established in this seed record.
Timeline events
BSC Token Hub exploit disclosed2022-10-06
BNB Chain reported an irregular cross-chain transfer involving BSC Token Hub and coordinated a temporary network suspension while the exploit was contained.
The nominal minted value should not be confused with the smaller amount reported as moved beyond immediate control.
BNB Smart Chain resumed after coordinated response2022-10-07
Validators resumed BNB Smart Chain after an upgrade and coordinated containment measures, while BSC Token Hub remained the incident focus.
This event records network resumption, not resolution of the unrecovered amount.
BSC Token Hub cross-chain transfers re-enabled after urgent patch2022-10-12
BNB Chain deployed an urgent cross-chain infrastructure patch and reported that previously paused cross-chain transfers would be re-enabled after the upgrade took effect.
This bridge-specific event is separate from the BNB Smart Chain validator pause and resume.
Native BSC Token Hub path retired during BNB Chain Fusion2024-11-19
BNB Chain disabled cross-chain communication between BNB Beacon Chain and BNB Smart Chain during the final Beacon Chain sunset, retiring the historical native bridge path.
The later BNB Chain Bridge aggregation interface is distinct from the retired native BSC Token Hub path.
Evidence records
- BNB Chain Ecosystem UpdateBNB Chain · Tier 1 · High reliability · primary · 2022-10-07Claim scope: Incident Case
Initial official update on the irregular cross-chain transfer, network suspension, and response.
- BNB Chain: A Decentralized ResponseBNB Chain · Tier 1 · High reliability · primary · 2022-10-11Claim scope: Recovery
Official explanation of the forged-proof exploit, the two million BNB nominal amount, validator response, and approximately $100 million described as unrecovered.
- Attack Mints $569 Million Worth of BNB Tokens in BSC Bridge ExploitElliptic · Tier 1 · High reliability · secondary · 2022-10-07Claim scope: Amount
Blockchain analytics source supporting the approximately $569 million nominal value and cross-chain movement context.
- BNB Chain FusionBNB Chain · Tier 1 · High reliability · primary · 2024-01-08Claim scope: Migration
Official source for the Beacon Chain sunset and retirement of cross-chain communication between Beacon Chain and BNB Smart Chain.
- BNB Chain: A Decentralized ResponseBNB Chain · Tier 1 · High reliability · primary · 2022-10-11Claim scope: Restart
Primary source distinguishing chain resumption from bridge transfer re-enablement and describing the October 12 upgrade.
- Technology Update of BNB Chain in Oct 2022BNB Chain · Tier 1 · High reliability · primary · 2022-11-08Claim scope: Restart
Primary retrospective confirmation that the urgent patch re-enabled cross-chain infrastructure.
- BNB Chain: A Decentralized ResponseBNB Chain · Tier 1 · High reliability · primary · 2022-10-11Claim scope: Incident Case
Event-scoped duplicate of bir_src_000022: the official retrospective supports the BSC Token Hub exploit, nominal mint, validator response, and unrecovered amount; the original record remains recovery-scoped to bir_ev_000017.
- BNB Chain Ecosystem UpdateBNB Chain · Tier 1 · High reliability · primary · 2022-10-07Claim scope: Restart
Event-scoped duplicate of bir_src_000021: the official update supports the emergency suspension and return of BNB Smart Chain operation; the original record remains incident-scoped to bir_ev_000016.
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 realized economic loss and later recovery or liquidation outcomes require further review.
- The bridge was retired later through BNB Chain Fusion, not solely as a direct incident response.
Conflicting claims
Incident value
Reported values: 2,000,000 BNB minted and taken, nearly $570 million nominal value · About $100 million reported as moved off-chain and unrecovered
Current treatment: Retain both figures because they measure different scopes: nominal assets created versus estimated unrecovered assets moved beyond immediate control.
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.