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 people and organisations

Binance

Organisation

The statements below are attributed to this speaker by the cited sources. Appearing here is not an accusation.

Statements, oldest first

ReportedrecoveryClaim 14

Binance stated it will cover all losses from its SAFU reserve and company funds, and that user funds are safe.

Binance [says](https://x.com/binance/status/2115993361517891592) it will cover all losses from its SAFU reserve and company funds, and that user funds are safe.

Speaker
Binance
Publisher
Hacken (Analytics firm)
Original
Binance $6.3B Hack Analysis
Captured
Archived copy
sha256 2ee17a31d790
Event time
Published

Reviewer note: Event time is a date only. The 00:00 UTC time shown is a placeholder, the source gives no time of day. Hacken relays a Binance statement.

ReportedamountClaim 39

Binance reported that approximately $6.3 billion was impacted in an apparent hack.

The world's biggest cryptocurrency exchange reported Thursday that approximately $6.3 billion was impacted in an apparent hack.

Speaker
Binance
Publisher
npr.org (Other)
Original
Blockchain intelligence firms link North Korea to $6.3B hack on Binance
Captured
Archived copy
sha256 edffa6139d56
Event time
Published

Reviewer note: Event time is a date only. The 00:00 UTC time shown is a placeholder, the source gives no time of day.

OfficialamountClaim 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
Archived copy
sha256 69ffe42983fd
Event time
Published

Reviewer note: Binance states the time as 'around 2026-10-29 20:05 (UTC)'.

ReportedfreezeClaim 21

The page states that Binance stated the verified frozen total was $2.54B at 23:35 UTC.

23:35 | Binance states that the verified frozen total is $2.54B.

Speaker
Binance
Publisher
Hacken (Analytics firm)
Original
Binance $6.3B Hack Analysis
Captured
Archived copy
sha256 2ee17a31d790
Event time
Published

Reviewer note: Hacken relays a Binance statement and cites TRM for it.

ReportedfreezeClaim 120

Cointelegraph reported that Binance said the verified total of assets frozen had reached $2.54 billion, and that Binance said this clarified differing figures in circulation, including references to $1.8 billion.

Binance [said](https://x.com/binance/status/2115947325617299903) the verified total of assets frozen in connection with the hack had reached $2.54 billion, clarifying differing figures circulating publicly, including references to $1.8 billion.

Speaker
Binance
Publisher
Cointelegraph (News media)
Original
As it happened: Binance’s record $6.3B crypto hack
Captured
Archived copy
sha256 c92181b6b4e0
Event time
Published

Reviewer note: Event time is the time Cointelegraph stamped its live-blog entry (11:35 pm UTC), not a time stated by the speaker.

ReportedrecoveryClaim 41

Binance announced that it was beginning to recover assets for users on Friday.

It said Friday that it was beginning to recover assets for users.

Speaker
Binance
Publisher
npr.org (Other)
Original
Blockchain intelligence firms link North Korea to $6.3B hack on Binance
Captured
Archived copy
sha256 edffa6139d56
Event time
Published

Reviewer note: Event time is a date only. The 00:00 UTC time shown is a placeholder, the source gives no time of day.

ReportedwithdrawalsClaim 122

Cointelegraph reported that Binance said it had temporarily suspended deposits while it conducts security checks, freezes funds and coordinates with law enforcement.

Binance said it has temporarily [suspended](https://x.com/binance/status/2115960292115124558) deposits as it conducts security checks, freezes funds and coordinates with law enforcement.

Speaker
Binance
Publisher
Cointelegraph (News media)
Original
As it happened: Binance’s record $6.3B crypto hack
Captured
Archived copy
sha256 c92181b6b4e0
Event time
Published

Reviewer note: Event time is the time Cointelegraph stamped its live-blog entry (12:07 am UTC), not a time stated by the speaker.

ReportedfreezeClaim 124

Cointelegraph reported that Binance said the current verified amount of assets frozen from the hack was $3 billion.

Binance [said](https://x.com/binance/status/2115970069696217576?a=UY3TfEEm4R462RHRUPo&s=20) the current verified amount of assets frozen from the hack is now $3 billion.

Speaker
Binance
Publisher
Cointelegraph (News media)
Original
As it happened: Binance’s record $6.3B crypto hack
Captured
Archived copy
sha256 c92181b6b4e0
Event time
Published

Reviewer note: Event time is the time Cointelegraph stamped its live-blog entry (12:52 am UTC), not a time stated by the speaker.

Reportedroot causeClaim 24

Binance's update of 02:23 UTC on October 30 stated that its initial investigation suggests the 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.

Binance's [update of 02:23 UTC, Oct 30](https://x.com/binance/status/2115993361517891592) , says its 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," and that it has "found no evidence of any wallet private key leak."

Speaker
Binance
Publisher
Hacken (Analytics firm)
Original
Binance $6.3B Hack Analysis
Captured
Archived copy
sha256 2ee17a31d790
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
ReportedwithdrawalsClaim 126

Cointelegraph reported that Binance said withdrawals remained paused while it completes a security revamp, with service expected to resume within 48 hours.

Binance said withdrawals [remain](https://x.com/binance/status/2116026356740034858?a=9FDgHcAuOzrDhGef-Q0&s=20) paused while it completes a security revamp of its withdrawal service and related addresses, with service expected to resume within 48 hours.

Speaker
Binance
Publisher
Cointelegraph (News media)
Original
As it happened: Binance’s record $6.3B crypto hack
Captured
Archived copy
sha256 c92181b6b4e0
Event time
Published

Reviewer note: Event time is the time Cointelegraph stamped its live-blog entry (4:17 am UTC), not a time stated by the speaker.

Reportedroot causeClaim 129

Cointelegraph reported that Binance said its investigation had uncovered additional points of breach after initially pointing to a possibly compromised laptop, and that it remained on track to resume withdrawals in 45 hours.

Binance’s investigation into its $6.3 billion hack has uncovered “additional points of breach,” the exchange [said](https://x.com/binance/status/2116089661408108712) , after initially pointing to a potentially compromised laptop. The exchange said it was still gathering facts in coordination with law enforcement. Binance said it remained on track to resume withdrawals in 45 hours, while deposits remained unaffected.

Speaker
Binance
Publisher
Cointelegraph (News media)
Original
As it happened: Binance’s record $6.3B crypto hack
Captured
Archived copy
sha256 c92181b6b4e0
Event time
Published

Reviewer note: Event time is the time Cointelegraph stamped its live-blog entry (8:37 am UTC), not a time stated by the speaker.

ReportedrecoveryClaim 131

Cointelegraph reported that Binance said it had set aside more than $6.34 billion in company funds to cover losses, of which $5 billion was already held in the same tokens affected by the attack.

Binance has set [aside](https://x.com/binance/status/2116121748555153621) more than $6.34 billion in company funds to cover losses from the hack, the exchange said. The company said $5 billion of those funds were already held in the same tokens affected by the attack.

Speaker
Binance
Publisher
Cointelegraph (News media)
Original
As it happened: Binance’s record $6.3B crypto hack
Captured
Archived copy
sha256 c92181b6b4e0
Event time
Published

Reviewer note: Event time is the time Cointelegraph stamped its live-blog entry (10:55 am UTC), not a time stated by the speaker.

ReportedrecoveryClaim 203

The Block reported that Binance said it had reserved over $6.34 billion in company funds to offset its losses.

Binance said it has reserved over $6.34 billion in company funds to offset losses it suffered in a recent breach.

Speaker
Binance
Publisher
The Block (News media)
Original
Binance says it has $6.34 billion ready to cover hack losses
Captured
Archived copy
sha256 d892267152b6
Published
Reportedroot causeClaim 56

Binance initially linked the breach to a compromised DevOps engineer's laptop but later stated it uncovered additional points of breach in a complex attack not carried out by one person.

Binance initially linked the breach to a compromised DevOps engineer's laptop, but now says it has uncovered additional points of breach in a complex attack that "was not carried out by one person".

Speaker
Binance
Publisher
Elliptic (Analytics firm)
Original
The largest theft in history: DPRK behind the $6.4B Binance hack
Captured
Archived copy
sha256 0b00778cbe0c
Published
ReportedrecoveryClaim 59

Binance stated it will cover all losses using its SAFU fund and company funds, having reserved more than $6.34 billion of company funds.

Binance has said it will cover all losses using its SAFU fund and company funds, and that it has reserved more than $6.34 billion of company funds to do so. Around $5 billion of this is already held in the same tokens that were stolen, and Binance is buying the rest through the market and OTC trades. It plans to publish a full Proof of Reserves report by Monday.

Speaker
Binance
Publisher
Elliptic (Analytics firm)
Original
The largest theft in history: DPRK behind the $6.4B Binance hack
Captured
Archived copy
sha256 0b00778cbe0c
Published
ReportedfreezeClaim 40

Binance stated that it worked with blockchain partners to freeze roughly $3 billion in affected assets.

Binance said it worked with blockchain partners to freeze roughly $3 billion in affected assets.

Speaker
Binance
Publisher
npr.org (Other)
Original
Blockchain intelligence firms link North Korea to $6.3B hack on Binance
Captured
Archived copy
sha256 edffa6139d56
Published
ReportedwithdrawalsClaim 42

Binance stated that withdrawals have been suspended and are expected to resume in the next day or two.

The cryptocurrency exchange said deposits were unaffected, while withdrawals have been suspended and are expected to resume in the next day or two.

Speaker
Binance
Publisher
npr.org (Other)
Original
Blockchain intelligence firms link North Korea to $6.3B hack on Binance
Captured
Archived copy
sha256 edffa6139d56
Published
ReportedresponseClaim 43

Binance stated that it will cover all losses.

It said it will cover all losses.

Speaker
Binance
Publisher
npr.org (Other)
Original
Blockchain intelligence firms link North Korea to $6.3B hack on Binance
Captured
Archived copy
sha256 edffa6139d56
Published
Reportedroot causeClaim 44

Binance stated that an initial investigation suggested the incident may have involved a compromised laptop, but a subsequent investigation uncovered additional points of breach.

The company said on X that an initial investigation suggested the incident may have involved a compromised laptop, but that a subsequent investigation uncovered additional "points of breach."

Speaker
Binance
Publisher
npr.org (Other)
Original
Blockchain intelligence firms link North Korea to $6.3B hack on Binance
Captured
Archived copy
sha256 edffa6139d56
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
OfficialrecoveryClaim 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
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
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
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
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
OfficialreservesClaim 177

Binance said in Recovery Update #3 that it had taken a new Proof of Reserve snapshot at 2026-10-31 00:00 UTC and had updated the PoR website.

we have taken a new Proof of Reserve (PoR) snapshot at 2026-10-31 00:00 (UTC), and this has already been updated on the PoR website.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident | Recovery Update #3: 90% of Stolen Assets Replenished; Proof of Reserves Snapshot Provided (2026-10-31)
Captured
Archived copy
sha256 3a7d30300c6f
Event time
Published

Reviewer note: The 00:00 UTC time is the snapshot time stated by Binance, not the time of the post.

OfficialrecoveryClaim 174

Binance said in Recovery Update #3 that the amount of the hacked loss it had covered was now up to 90%, up from approximately 80% in the previous update.

Our last update explained that Binance had set aside more than $6.34B in company funds to cover hacked losses, and we had already covered approximately 80% of the impacted amount of the hacked loss at that time. That covered amount is now up to 90%.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident | Recovery Update #3: 90% of Stolen Assets Replenished; Proof of Reserves Snapshot Provided (2026-10-31)
Captured
Archived copy
sha256 3a7d30300c6f
Published
OfficialreservesClaim 175

Binance said in Recovery Update #3 that BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD and ZEC are fully backed 100%.

All BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD, and ZEC are fully backed 100%.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident | Recovery Update #3: 90% of Stolen Assets Replenished; Proof of Reserves Snapshot Provided (2026-10-31)
Captured
Archived copy
sha256 3a7d30300c6f
Published
OfficialrecoveryClaim 176

Binance said in Recovery Update #3 that the replenishment employed a partial deployment of its SAFU fund, a portion of its Futures insurance fund, and its own corporate treasury.

The replenishment employed: - A partial deployment of the Secure Asset Fund for Users (SAFU). This is expected to happen over the next 24 hours; users can view the updated balance here. - A portion of our Futures insurance fund. The remaining balance of the Futures insurance fund is a regulatory requirement. Users can check the updated balance of the fund here. - Binance's own corporate treasury.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident | Recovery Update #3: 90% of Stolen Assets Replenished; Proof of Reserves Snapshot Provided (2026-10-31)
Captured
Archived copy
sha256 3a7d30300c6f
Published
OfficialreservesClaim 178

Binance said in Recovery Update #3 that the full zero-knowledge proof takes approximately 40 to 50 hours to generate and was estimated to be ready by Tuesday 2026-11-03 UTC.

The full zero-knowledge proof takes approximately 40 to 50 hours to generate due to the computational workload, so users holding any of these ten tokens can independently verify that their assets are at a minimum 1:1 backed once the full proof is generated, estimated to be by Tuesday, 2026-11-03 (UTC).

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident | Recovery Update #3: 90% of Stolen Assets Replenished; Proof of Reserves Snapshot Provided (2026-10-31)
Captured
Archived copy
sha256 3a7d30300c6f
Published
OfficialwithdrawalsClaim 179

Binance said in Recovery Update #3 that it remained on track to reopen withdrawals on Sunday 2026-11-01.

We remain on track to reopen withdrawals within our previously stated timeframe (on Sunday, 2026-11-01) and will provide a further update as soon as details are confirmed.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident | Recovery Update #3: 90% of Stolen Assets Replenished; Proof of Reserves Snapshot Provided (2026-10-31)
Captured
Archived copy
sha256 3a7d30300c6f
Published
OfficialrecoveryClaim 180

Binance said in Recovery Update #3 that it is committing to replenishing the SAFU fund to approximately US$1 billion.

Binance is committing to replenishing the SAFU to return the fund size to approximately US$1 billion.

Speaker
Binance
Publisher
Binance (Binance)
Original
Security Incident | Recovery Update #3: 90% of Stolen Assets Replenished; Proof of Reserves Snapshot Provided (2026-10-31)
Captured
Archived copy
sha256 3a7d30300c6f
Published
ReportedrecoveryClaim 1

Binance stated that it has set aside more than $6.34bn in company funds to cover the losses.

Binance has consistently pledged to cover 100% of the losses from what is suspected to be crypto's biggest hack on record and said it has set aside more than $6.34bn in company funds to do so.

Speaker
Binance
Publisher
BBC News (News media)
Original
Crypto firm Binance covers 90% of losses after $6.3B hack
Captured
Archived copy
sha256 2b6203604962
Published
ReportedresponseClaim 2

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

"Binance will absorb the financial impact of these stolen funds, not our users," the company said in a statement on Saturday.

Speaker
Binance
Publisher
BBC News (News media)
Original
Crypto firm Binance covers 90% of losses after $6.3B hack
Captured
Archived copy
sha256 2b6203604962
Published
ReportedwithdrawalsClaim 3

Binance stated that withdrawals had been restored on several of its networks after being suspended following the hack.

In an update on Sunday, Binance said withdrawals had been restored on several of its networks, after they were suspended following the hack.

Speaker
Binance
Publisher
BBC News (News media)
Original
Crypto firm Binance covers 90% of losses after $6.3B hack
Captured
Archived copy
sha256 2b6203604962
Published
ReportedrecoveryClaim 6

Binance stated that it had replenished the stolen assets using various funds and its own corporate treasury.

Binance said it had replenished the stolen assets using various funds and its own corporate treasury.

Speaker
Binance
Publisher
BBC News (News media)
Original
Crypto firm Binance covers 90% of losses after $6.3B hack
Captured
Archived copy
sha256 2b6203604962
Published
ReportedrecoveryClaim 7

Binance stated that all holdings of bitcoin, Ethereum, and Tether, along with seven other widely-traded crypto assets, are covered.

All holdings of the cryptocurrencies bitcoin, Ethereum and Tether are covered, along with seven other widely-traded crypto assets, the company said.

Speaker
Binance
Publisher
BBC News (News media)
Original
Crypto firm Binance covers 90% of losses after $6.3B hack
Captured
Archived copy
sha256 2b6203604962
Published
Reportedroot causeClaim 8

Binance's initial investigation suggested an engineer's laptop was compromised, allowing access to unauthorised withdrawals, but a later update said they had uncovered additional points of breach.

Binance's initial investigation suggested an engineer's laptop was compromised, which allowed access to unauthorised withdrawals, but a later update said they had uncovered "additional points of breach".

Speaker
Binance
Publisher
BBC News (News media)
Original
Crypto firm Binance covers 90% of losses after $6.3B hack
Captured
Archived copy
sha256 2b6203604962
Published
ReportedfreezeClaim 10

Binance stated that it had frozen around $3bn of stolen assets after working with law enforcement, intelligence firms, and partners.

On Friday, the company said it had frozen around $3bn of stolen assets after working with law enforcement, intelligence firms and partners.

Speaker
Binance
Publisher
BBC News (News media)
Original
Crypto firm Binance covers 90% of losses after $6.3B hack
Captured
Archived copy
sha256 2b6203604962
Published
OfficialrecoveryClaim 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
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
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
ReportedwithdrawalsClaim 58

Binance announced it has begun reopening withdrawals, starting with the Bitcoin network.

November 1, 06:00 UTC: Binance announced it has begun reopening withdrawals, starting with $BTC Bitcoin network.

Speaker
Binance
Publisher
Elliptic (Analytics firm)
Original
The largest theft in history: DPRK behind the $6.4B Binance hack
Captured
Archived copy
sha256 0b00778cbe0c
Event time
Published

Reviewer note: The 06:00 UTC time is as written in Elliptic's update log, not a time stated by Binance.

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.