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 sources

Security Incident Update (2026-10-30)

Publisher
Binance (Binance)
Original
https://www.binance.com/en/support/announcement/detail/c5a8729a97ac486d963784d96c5642d7
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. The text hash is of the text extracted from it, which is what is compared between captures.

Captured (UTC)Fetched viaHTTPRaw sha256Text sha256Text changed
http2005c94a3686cb15e66feb712e82a99cc13572251075ed7fe8623f9adf31f26b596ad9583090932624436dd83ee63529f19392e1f9a481384886fb4a30ecfda1b9fNo

Changes between captures

No text changes detected between captures of this source.

Claims quoted from this source

Officialroot causeClaim 280

Binance said in its first 30 October update that its initial investigation suggested a compromised DevOps engineer's laptop may have let an attacker reach a service container and submit unauthorized withdrawals.

Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident Update (2026-10-30)
Captured
Archived copy
sha256 5c94a3686cb1
Event time
Published
Officialroot causeClaim 281

Binance said in its first 30 October update that it had found no evidence of any wallet private key leak.

We have found no evidence of any wallet private key leak.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident Update (2026-10-30)
Captured
Archived copy
sha256 5c94a3686cb1
Event time
Published
OfficialresponseClaim 282

Binance told users in its first 30 October update to rely only on official Binance channels for updates.

Please rely only on official Binance channels for updates.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident Update (2026-10-30)
Captured
Archived copy
sha256 5c94a3686cb1
Event time
Published
OfficialattributionClaim 283

Binance said in its first 30 October update that it was working with law enforcement partners to confirm the identity of the criminals.

We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident Update (2026-10-30)
Captured
Archived copy
sha256 5c94a3686cb1
Event time
Published
Officialroot causeClaim 161

Binance said in its Security Incident Update dated 2026-10-30 that its initial investigation suggested the incident may involve a compromised DevOps engineer's laptop, which allowed an attacker to access a service container and submit unauthorized withdrawal transactions, and that it had found no evidence of any wallet private key leak.

Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We have found no evidence of any wallet private key leak.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident Update (2026-10-30)
Captured
Archived copy
sha256 5c94a3686cb1
Published
OfficialamountClaim 162

Binance said in its Security Incident Update dated 2026-10-30 that the estimated total impact sits at around $6.3B.

The estimated total impact sits at around $6.3B.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident Update (2026-10-30)
Captured
Archived copy
sha256 5c94a3686cb1
Published
OfficialfreezeClaim 163

Binance said in its Security Incident Update dated 2026-10-30 that it had worked with blockchain partners to freeze affected assets, with about $3 billion frozen on-chain so far.

We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident Update (2026-10-30)
Captured
Archived copy
sha256 5c94a3686cb1
Published
OfficialrecoveryClaim 164

Binance said in its Security Incident Update dated 2026-10-30 that it will cover all losses from the SAFU fund and the company's funds, and that user funds are safe.

Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident Update (2026-10-30)
Captured
Archived copy
sha256 5c94a3686cb1
Published
OfficialwithdrawalsClaim 165

Binance said in its Security Incident Update dated 2026-10-30 that as an immediate precaution it had temporarily suspended withdrawals, revoked the affected address authorisation, and engaged law enforcement and blockchain intelligence partners.

As an immediate precaution, Binance has: - temporarily suspended withdrawals while security checks are completed; - revoked the affected address authorisation; - engaged law enforcement and blockchain intelligence partners to trace and recover funds.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident Update (2026-10-30)
Captured
Archived copy
sha256 5c94a3686cb1
Published
OfficialresponseClaim 166

Binance added a note to its Security Incident Update dated 2026-10-30 saying the announcement was updated on 2026-10-30 to clarify that deposits remain unaffected.

Note: This announcement was updated on 2026-10-30 to clarify deposits remain unaffected and continue to operate as normal.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident Update (2026-10-30)
Captured
Archived copy
sha256 5c94a3686cb1
Published