Independent record. Not associated with, endorsed by or operated by Binance. This site is read-only: there is nothing to sign in to, pay for or connect.

All sources

Security Incident Update #2 (2026-10-30)

Publisher
Binance (Binance)
Original
https://www.binance.com/en/support/announcement/detail/d3306d9dca5243548c813b605e1d1751
Published
First seen
Last captured
Watched for edits
Yes, captured again on a schedule

Capture history

Newest first. The raw hash is the SHA-256 of the stored copy exactly as fetched. We keep the copy privately and publish its hash. The text hash is of the text extracted from it, which is what is compared between captures.

Captured (UTC)Fetched viaHTTPRaw sha256Text sha256Text changed
http20069ffe42983fd048c2bad90cc83156be3267b46aefdbb10f46a33dd7c4a020c8bfaf6cd5957f6cdab1282edbf7d2729e32b0c8bd1d46b024f70a81b3d80f24496No

Changes between captures

No text changes detected between captures of this source.

Claims quoted from this source

OfficialamountStatement 167

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.

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.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident Update #2 (2026-10-30)
Captured
Stored copy
sha256 69ffe42983fd
Event time
Published
OfficialfreezeStatement 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
Stored copy
sha256 69ffe42983fd
Event time
Published
Officialroot causeStatement 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
Stored copy
sha256 69ffe42983fd
Event time
Published
OfficialwithdrawalsStatement 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
Stored copy
sha256 69ffe42983fd
Event time
Published
OfficialrecoveryStatement 286

Binance said it would cover all stolen funds through its SAFU fund and its corporate treasury.

Binance will cover all stolen funds related to this incident through our Secure Asset Fund for Users (SAFU) and our corporate treasury.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident Update #2 (2026-10-30)
Captured
Stored copy
sha256 69ffe42983fd
Event time
Published
Officialroot causeStatement 287

Binance said in its second 30 October update that it expected to share further technical findings within about 48 hours.

We expect to share further technical findings within about 48 hours once they have been verified and their disclosure will not compromise ongoing investigative efforts.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident Update #2 (2026-10-30)
Captured
Stored copy
sha256 69ffe42983fd
Event time
Published
OfficialresponseStatement 288

Binance said it would publish a detailed technical report on what happened and the safeguards being added.

we will provide a detailed technical report outlining what happened, the lessons learned and the additional safeguards being implemented.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident Update #2 (2026-10-30)
Captured
Stored copy
sha256 69ffe42983fd
Event time
Published
OfficialresponseStatement 289

Binance told users in its second 30 October update to follow only its official channels or contact official Customer Support for verified updates.

For verified updates, please follow Binance's official channels only, or contact us directly through the official Customer Support.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident Update #2 (2026-10-30)
Captured
Stored copy
sha256 69ffe42983fd
Event time
Published
OfficialresponseStatement 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
Stored copy
sha256 69ffe42983fd
Published
OfficialrecoveryStatement 169

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.

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
Stored copy
sha256 69ffe42983fd
Published
OfficialreservesStatement 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
Stored copy
sha256 69ffe42983fd
Published
OfficialwithdrawalsStatement 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.

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