Independent record. Not associated with, endorsed by or operated by Binance. We will never ask you to connect a wallet, log in or pay to recover funds.

All claims

Binance said in its Security Incident Update #2 that it had set aside more than $6.34B in company funds, with $5B held in the exact impacted token assets, which it said meant it had covered approximately 80% of the impacted amount.

This line is our short summary of the quote below. The quote is the evidence.

OfficialrecoveryClaim 169

We have already set aside more than $6.34B in company funds, with $5B held in the exact impacted token assets that were stolen, such as USDC, USDT, BTC, ETH, BNB, etc. This means that we have already covered approximately 80% of the impacted amount.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident Update #2 (2026-10-30)
Captured
Archived copy
sha256 69ffe42983fd
Published

On the timeline

Figures from this claim

Cited in theories

Other claims from the same source

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.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident Update #2 (2026-10-30)
Captured
Archived copy
sha256 69ffe42983fd
Published
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.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident Update #2 (2026-10-30)
Captured
Archived copy
sha256 69ffe42983fd
Published
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.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident Update #2 (2026-10-30)
Captured
Archived copy
sha256 69ffe42983fd
Published
OfficialfreezeClaim 170

Binance said in its Security Incident Update #2 that it had worked with law enforcement, blockchain intelligence firms, asset issuers and industry partners to trace and freeze affected assets, and that approximately $3 billion had been frozen on-chain to date.

Worked with law enforcement, blockchain intelligence firms, asset issuers and industry partners to trace and freeze affected assets. Approximately $3 billion has been frozen on-chain to date.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident Update #2 (2026-10-30)
Captured
Archived copy
sha256 69ffe42983fd
Published
OfficialresponseClaim 168

Binance said in its Security Incident Update #2 that Binance will absorb the financial impact of the stolen funds, not its users.

We want to be clear about our commitment: Binance will absorb the financial impact of these stolen funds, not our users.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident Update #2 (2026-10-30)
Captured
Archived copy
sha256 69ffe42983fd
Published