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 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.

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

OfficialrecoveryClaim 182

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
Archived copy
sha256 fa8f87302d54
Published

On the timeline

Other claims from the same source

OfficialrecoveryClaim 723

Binance stated that it had already covered approximately 90% of the impacted amount, up from approximately 80% in the prior update.

As shared in our previous update, Binance had already covered approximately 90% of the impacted amount, up from approximately 80% in the prior update.

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

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 ...

OfficialrecoveryClaim 722

Binance stated that it will absorb the financial impact of the stolen funds rather than passing the losses to users.

Binance will absorb the financial impact of the stolen funds, not our users.

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

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 ...

OfficialresponseClaim 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
Archived copy
sha256 fa8f87302d54
Published
Officialroot causeClaim 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
Archived copy
sha256 fa8f87302d54
Published
OfficialwithdrawalsClaim 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
Archived copy
sha256 fa8f87302d54
Event time
Published

Reviewer note: 06:00 UTC is the start of the window Binance announced, not a time at which withdrawals were confirmed open.