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 | Recovery Update #4: Withdrawals Resume in Phases (2026-11-01)

Publisher
Binance (Binance)
Original
https://www.binance.com/en/support/announcement/detail/73911fb819b240f88b88256bdd318eda
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
http200fa8f87302d54ea3181dc3399e38e00ba34c2edb3623bf2f6d350e5017138a0633176bb701e51c3dbb421fe6433ae7e0793dcf3b47f6a365329727956d34edb4aNo

Changes between captures

No text changes detected between captures of this source.

Claims quoted from this source

OfficialrecoveryStatement 294

Binance said on 1 November that it had covered approximately 95% of the impacted amount, up from 90%.

Binance has now covered approximately 95% of the impacted amount, up from 90% in our prior update.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident | Recovery Update #4: Withdrawals Resume in Phases (2026-11-01)
Captured
Stored copy
sha256 fa8f87302d54
Event time
Published
OfficialresponseStatement 406

Binance said on 1 November that it will bear the financial impact of the stolen funds and that the losses will not be passed on to users.

Our commitment remains unchanged: Binance will bear the financial impact of the stolen funds. These losses will not be passed on to users.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident | Recovery Update #4: Withdrawals Resume in Phases (2026-11-01)
Captured
Stored copy
sha256 fa8f87302d54
Event time
Published
OfficialrecoveryStatement 182

Binance said in Recovery Update #4 that it had now covered approximately 95% of the impacted amount, up from 90% in the prior update, with the outstanding 5% in less liquid tokens outside the top ten.

Binance has now covered approximately 95% of the impacted amount, up from 90% in our prior update. The outstanding 5% are tokens outside the top ten listed above, and are less liquid in the market and take longer time to source at the required scale.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident | Recovery Update #4: Withdrawals Resume in Phases (2026-11-01)
Captured
Stored copy
sha256 fa8f87302d54
Published
Officialroot causeStatement 183

Binance said in Recovery Update #4 that it will publish a post-incident report with further details once the investigation is complete.

Once the investigation is complete, we will publish a post-incident report with further details on the incident.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident | Recovery Update #4: Withdrawals Resume in Phases (2026-11-01)
Captured
Stored copy
sha256 fa8f87302d54
Published
OfficialresponseStatement 184

Binance said in Recovery Update #4 that deposit services remain open and are not affected by the incident.

Deposit services remain open and are not affected by the incident.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident | Recovery Update #4: Withdrawals Resume in Phases (2026-11-01)
Captured
Stored copy
sha256 fa8f87302d54
Published
OfficialwithdrawalsStatement 181

Binance said in Recovery Update #4 that it was preparing to resume phase one of withdrawals on 2026-11-01 between 06:00 and 09:00 UTC.

Binance is preparing to resume phase one of withdrawals on 2026-11-01 between 06:00 and 09:00 (UTC).

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident | Recovery Update #4: Withdrawals Resume in Phases (2026-11-01)
Captured
Stored copy
sha256 fa8f87302d54
Event time
Published