OfficialamountClaim 167
At around 2026-10-29 20:05 (UTC), our hot wallets were compromised, resulting in a loss of approximately $6.3B USD worth of token assets.
Reviewer note: Binance states the time as 'around 2026-10-29 20:05 (UTC)'.
Binance said in its Security Incident Update #2 that at around 20:05 UTC on 2026-10-29 its hot wallets were compromised, resulting in a loss of approximately $6.3B USD worth of token assets.
This line is our short summary of the quote below. The quote is the evidence.
Flagged as conflicting
- Binance puts the loss at about $6.3B. Elliptic counts $6.43B and says its total excludes a further $169 million that left after withdrawals were suspended. The sources do not say whether the gap comes from pricing time, chains counted or other scope. Compare with Elliptic said $6.43 billion in cryptoassets was stolen from Binance on 29 October 2026. (Elliptic). Side by side
- Binance says the hot wallets were compromised at around 20:05 UTC. Chainalysis says funds began leaving at around 4:20 p.m. ET. The sources do not say whether these refer to the same first transfer. Compare with Chainalysis said funds began leaving Binance hot wallets at around 4:20 p.m. ET on 29 October. (Chainalysis). Side by side
On the timeline
Figures from this claim
- Total stolen: $6,300,000,000.00 as of
Other claims from the same source
OfficialreservesClaim 739
Binance plans to run an initial Proof Of Reserves snapshot in 12 hours and have the result ready by Monday 2026-11-02.
We plan to run an initial Proof Of Reserves snapshot in 12 hours and have the result ready by Monday 2026-11-02.
Reviewer note: Automatic: exact quote from an official page, published as 'official' without human review. Official means only that the party said it. Pull it with review.py revoke ID --note ...
OfficialwithdrawalsClaim 738
Binance stated that it temporarily suspended withdrawals while conducting additional security reviews and implementing remediation measures.
Temporarily suspended withdrawals while conducting additional security reviews, implementing remediation measures and validating the integrity of affected systems.
Reviewer note: Automatic: exact quote from an official page, published as 'official' without human review. Official means only that the party said it. Pull it with review.py revoke ID --note ...
OfficialreservesClaim 173
Binance said in its Security Incident Update #2 that it was buying the remaining 20% of the lost token assets, planned an initial Proof of Reserves snapshot in 12 hours, and expected the result by Monday 2026-11-02.
We are buying the remaining 20% of the lost token assets. We plan to run an initial Proof Of Reserves snapshot in 12 hours and have the result ready by Monday 2026-11-02.
OfficialwithdrawalsClaim 172
Binance said in its Security Incident Update #2 that its tech team targeted starting to resume withdrawals within approximately 34 hours, subject to security checks, on a phased approach.
The tech team targets to start resuming the withdrawal service within approximately 34 hours, subject to the completion of security checks. This will proceed on a phased approach.
Officialroot causeClaim 171
Binance said in its Security Incident Update #2 that its subsequent investigation had uncovered additional points of breach beyond a possibly compromised laptop, and that it had found no evidence that wallet private keys were leaked.
Our initial investigation suggested that the incident may involve a compromised laptop, however, our subsequent investigation has uncovered additional points of breach. At this stage, we have found no evidence that wallet private keys were leaked.