# Binance Covers 95% After $6.3B Hack; Withdrawals Resume

![Binance Covers 95% After $6.3B Hack; Withdrawals Resume](hero.webp)

**Binance says it has replenished approximately 95% of the crypto assets affected by its October 29, 2026, security breach and is restarting customer withdrawals in phases on November 1.** Its previous update reported 90% replenishment; the newer figure and the first withdrawal reopening are material developments. Binance estimates that the original hot-wallet breach affected about **$6.3 billion** in token assets. **Replacing stolen assets is not the same as recovering coins from the attackers, and the resumption of some withdrawal routes does not mean every token and network is operating normally.**

The exchange says BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD and ZEC are now **fully backed**. It is still sourcing less-liquid tokens that make up the final approximately **5%** of affected assets. [Binance's November 1 announcement](https://www.binance.com/en-GB/support/announcement/security-incident-recovery-update-4-withdrawals-resume-in-phases-2026-11-01-73911fb819b240f88b88256bdd318eda) listed withdrawal routes scheduled for the first phase. [AFP independently reported](https://www.afp.com/en/binance-says-resuming-withdrawals-after-major-hack) that Bitcoin-network withdrawals began reopening, while availability of other routes was subject to the staged rollout.

> **Short answer:** As of Binance's November 1 recovery update, it said **95% of affected assets had been replaced or covered**, compared with 90% on October 31. **Bitcoin withdrawals started reopening**, and other specified networks and assets were being restored in stages. This does **not** mean 95% of stolen coins have been retrieved, the remaining 5% has been completed, every withdrawal is available, or the final post-incident security findings have been published. Customers should check the live status of their particular **asset and blockchain network** before transferring funds.

**Terenval's editorial assessment:** The most useful measure of an exchange's recovery is not a single percentage. Users need to distinguish **asset backing, usable withdrawal access and evidence of security remediation**. A platform can report substantial replenishment while a customer still cannot withdraw a particular token. Conversely, a withdrawal route may reopen before every affected asset has been sourced. The distinctions matter more than the headline percentage alone.

## What happened

**Direct summary:** Binance's October 31 recovery statement said approximately **90%** of affected assets had been replenished and that ten major cryptocurrencies were fully backed. On **November 1**, the exchange increased the stated replenishment to **95%** and announced its first phased reopening of withdrawals, scheduled for **06:00–09:00 UTC**. Binance says the remaining tokens are harder to acquire in the required size because of thinner market liquidity. [Reuters reported the 95% update and phased resumption](https://www.reuters.com/legal/government/binance-resume-withdrawals-after-recovering-bulk-6-billion-stolen-funds-2026-11-01/); [CoinDesk reported that Bitcoin withdrawals were among the first to reopen](https://www.coindesk.com/markets/2026/11/01/binance-opens-crypto-withdrawals-in-phases-starting-with-bitcoin-following-usd6-3-billion-hack).

The original incident was reported by Binance as an unauthorized withdrawal event affecting exchange-controlled hot wallets at around **20:05 UTC on October 29**. Binance put the value of affected tokens at approximately **$6.3 billion**, reported that roughly **$3 billion had been frozen on-chain** by its October 30 update, and pledged to absorb customer losses using resources under its control. Those figures are reported by Binance and should not be treated as an independently audited final loss statement. See its [October 30 security update](https://www.binance.com/en-GB/support/announcement/security-incident-update-2-2026-10-30-d3306d9dca5243548c813b605e1d1751).

Binance says deposits remained available while withdrawals were temporarily suspended for security checks. The first withdrawal phase is designed to restore particular token/network combinations after operational readiness tests; later phases depend on further checks.

### At a glance: latest confirmed status

| Question | Position reported by November 1, 2026 |
| --- | --- |
| What happened? | Unauthorized transfers from Binance-controlled hot-wallet infrastructure on October 29 |
| Estimated incident value | Approximately **$6.3 billion**, according to Binance |
| Replenishment on October 30 | Approximately **80%** |
| Replenishment on October 31 | Approximately **90%** |
| Latest replenishment | Approximately **95%**, according to November 1 update |
| Remaining replacement gap | Approximately **5%**, primarily less-liquid affected tokens |
| Ten major affected assets | Binance says they are **100% backed**; this is not a claim about every listed asset |
| Customer withdrawals | First routes reopening from November 1; availability differs by asset and network |
| Proof-of-reserves snapshot | Taken **October 31 at 00:00 UTC**; final zk proof expected by **November 3**, according to Binance |
| Final forensic report | Not yet published in the official updates reviewed for this article |

### Recovery timeline: October 29 to November 1

| Date (UTC) | Event | What it establishes |
| --- | --- | --- |
| October 29, about 20:05 | Binance says its hot wallets were compromised | Time of the reported unauthorized transfers, not a completed root-cause finding |
| October 30 | Binance reports roughly $6.3B affected, about $3B frozen, and approximately 80% covered | Affected value, issuer/blockchain freezes and corporate replacement are separate quantities |
| October 31 | Binance says replacement reaches 90%; lists ten fully backed assets | Continued purchases; not full recovery of the stolen coins |
| October 31, 00:00 | New PoR snapshot time | A point-in-time reserve view, not a November 1 withdrawal availability report |
| November 1 | Binance says replacement reaches 95%; first withdrawal phase begins | Operational reopening on selected routes, not unrestricted service for all assets |
| November 3 (target) | Full zero-knowledge proof expected | A future verification milestone, not a published result at this article's information cutoff |

## What does Binance's 95% replenishment figure actually mean?

**It means Binance says it has sourced replacement value or token holdings corresponding to approximately 95% of the assets affected by the hack. It does not mean investigators have retrieved 95% of the stolen tokens.** The exchange has described purchases through ordinary markets and over-the-counter (OTC) channels, financed through its corporate treasury and designated emergency or insurance resources.

That distinction is fundamental. Consider three separate responses to a theft:

1. **Freezing:** Issuers or other parties restrict movement of certain stolen tokens, where technically and legally possible. The coins may remain on addresses associated with the attackers and may not yet be under Binance's control.
2. **Recovering:** Law enforcement, issuers and investigators actually return assets or otherwise restore control to the rightful holder. A freeze does not itself prove that this has happened.
3. **Replenishing:** The exchange uses other funds to buy or allocate replacement assets so that customer balances can remain supported even while the originally stolen assets have not been returned.

The source of replacement matters. [Binance's October 31 update](https://www.binance.com/en-GB/support/announcement/security-incident-recovery-update-3-90-of-stolen-assets-replenished-proof-of-reserves-snapshot-provided-2026-10-31-1fdf1f61559c401da0435895ffcccb62) identifies a portion of the **Secure Asset Fund for Users (SAFU)**, an allocation from its **futures insurance fund**, and corporate treasury resources. The exchange says these are company-controlled resources, it intends to replenish SAFU toward approximately **$1 billion**, and the remaining insurance-fund balance stays above its stated internal requirements. These are Binance's descriptions, not an independently verified assessment of future stress resilience.

### Why 95% and 100% are not contradictory

The two percentages use **different denominators**. Binance says an aggregate 95% of the affected assets has been replenished, while ten named asset categories already have complete reported backing. The last 5% consists of other assets. Therefore, it would be incorrect to say either that all Binance assets remain 5% short or that 100% of every affected token has been restored.

A useful illustrative calculation—not a new forensic estimate—is that **5% of $6.3 billion is approximately $315 million**. This rough dollar equivalent is sensitive to changing token prices, the exact scope of the replenishment ratio and the company's accounting methodology. It should **not** be published as a confirmed outstanding loss or amount owed to specific users. The key published fact remains Binance's **approximately 5%** remaining replacement share.

## Which Binance withdrawals are reopening?

Binance's November 1 announcement listed the following **first-phase networks and assets**. The list describes the planned phased rollout; it is not a guarantee that an individual withdrawal will succeed at every moment. For a particular transaction, the in-account withdrawal page and current network-status notice take priority over a news article.

| Network / withdrawal rail | Assets listed for first phase |
| --- | --- |
| Bitcoin (BTC) | BTC |
| Ethereum (ETH) | ETH, USDT, USDC |
| BNB Smart Chain (BSC) | BNB, USDT, USDC |
| Tron (TRX) | TRX, USDT |
| Solana (SOL) | SOL, USDT, USDC |
| XRP Ledger | XRP |
| Zcash (ZEC) | ZEC |
| Dogecoin (DOGE) | DOGE |
| TON | USDT, GRAM |
| Polygon | POL, USDT, USDC |
| Avalanche C-Chain | AVAX, USDT, USDC |
| Arbitrum | ETH, USDT, USDC, ARB |
| Base | ETH, USDC |
| Optimism / OP Mainnet | ETH, USDT, USDC |
| Sui | SUI |

This table is a condensed transcription of Binance's [official November 1 rollout announcement](https://www.binance.com/en-GB/support/announcement/security-incident-recovery-update-4-withdrawals-resume-in-phases-2026-11-01-73911fb819b240f88b88256bdd318eda). Binance said it was prioritizing demand and would add further routes after security and stability checks. [AFP reported Bitcoin withdrawals had begun reopening](https://www.afp.com/en/binance-says-resuming-withdrawals-after-major-hack), while later rollouts may be uneven and subject to processing delays.

**A crucial detail:** USDT or USDC on Ethereum is not interchangeable with USDT or USDC on Tron, BSC, Solana or an Ethereum Layer 2. A wallet address, token symbol or supported asset name does not establish that a *specific withdrawal network* is live. Sending funds via an incompatible network can lead to a difficult or impossible recovery.

### Are deposits open, too?

In its November 1 statement, Binance said **deposit services remained open** and had not been affected by the withdrawal suspension. This does not eliminate the need to check a deposit address, token, memo or network in the user's authenticated account before transferring funds. Nor does it guarantee that a pending deposit is already credited.

## What is Binance's proof of reserves—and what can users verify?

**Proof of reserves (PoR)** is a mechanism for showing that a custodian holds specified assets against specified customer balances at a particular point in time. Binance uses a **Merkle-tree-based inclusion process** and **zk-SNARK cryptographic proofs** to help customers verify the inclusion of account data and certain aggregate statements. See Binance's [PoR methodology](https://www.binance.com/en/proof-of-reserves) and [account verification instructions](https://www.binance.com/en/support/faq/detail/815b25f0cb054bdd9d35eccc408fe981).

Binance said it took a new snapshot on **October 31, 2026, at 00:00 UTC** and updated the PoR site. The exchange estimated that generating the full zero-knowledge proof would require **40–50 hours**, with completion targeted for **November 3**. Those statements appeared in its [October 31 recovery update](https://www.binance.com/en-GB/support/announcement/security-incident-recovery-update-3-90-of-stolen-assets-replenished-proof-of-reserves-snapshot-provided-2026-10-31-1fdf1f61559c401da0435895ffcccb62).

The **snapshot time matters**. It predates the November 1 announcement that replenishment had reached 95%, so readers should not treat the snapshot alone as an independent confirmation of every later status claim. Likewise, an updated PoR page is not equivalent to a complete independent corporate financial audit or a security investigation.

### What proof of reserves can and cannot establish

| Evidence | What it may help show | What it does not establish on its own |
| --- | --- | --- |
| Exchange reserve-address holdings | Assets exist at disclosed addresses at a snapshot | Absence of undisclosed debts or borrowed assets |
| Inclusion proof for a user balance | That the user's balance appears in the committed data set | That all off-chain liabilities are reported |
| Cryptographic aggregate proof | Consistency of specified balance calculations under the implemented method | Operational ability to process every withdrawal |
| Replenishment announcement | Management's stated progress replacing affected assets | Independent completion of purchases or return of stolen assets |
| Successful withdrawal by a customer | That one asset/network route processed that request | That all users and assets can withdraw without delay |
| Published incident post-mortem, if eventually provided | Findings about root cause and remediation | Immunity to future attacks |

### How should a Binance customer verify their own PoR entry?

Use the authenticated Binance account and its official **Proof of Reserves / Verification** instructions. Confirm the **audit date**, the **asset**, the **balance included**, and whether the final proof for that snapshot is **actually available**. Follow Binance's documented Merkle/zk-SNARK verification procedure rather than downloading a purported verifier from an unrelated message, browser advertisement or unsolicited support chat.

A correct inclusion check is useful evidence about the published dataset. It should be interpreted together with the stated scope and timing of the report, not as a guarantee of real-time solvency or unrestricted access to funds.

## Terenval analysis: the Three-Ledger Recovery Model

**Original editorial framework:** Terenval's **Three-Ledger Recovery Model** separates three questions that can otherwise become confused in headlines about a large exchange incident. This is an explanatory model, not an external accounting standard or a feature implemented by Terenval Wallet.

| Ledger | Main question | Evidence to seek | Typical misleading shortcut |
| --- | --- | --- | --- |
| **1. Incident and recovery ledger** | What was moved without authorization, frozen, returned or still missing? | Transaction tracing, issuer notices, documented recovery and asset-control records | Treating "frozen" as "returned" |
| **2. Customer backing ledger** | What assets does the exchange now hold against reported customer obligations? | Token-level replacement figures, PoR scope and timing, liabilities and independent assurance | Treating "95% replaced" as a complete balance-sheet audit |
| **3. Customer access ledger** | Can this user withdraw this asset through this network right now? | Live platform status, a valid withdrawal request, transaction ID and confirmations | Treating a reopened BTC route as universal reopening |

Our assessment is that **these ledgers can move at different speeds**. The original stolen assets could remain outside the exchange while replacement purchases support customer balances. A token could be covered on the backing ledger but unavailable through a temporarily suspended withdrawal route. A restored withdrawal pathway can function while investigations into stolen funds remain incomplete.

The model deliberately resists a simplistic "percentage recovered" headline. A more meaningful description of November 1 is: **Binance reports 95% replacement of affected assets and is restoring selected withdrawal pathways, while stolen-asset recovery, final proof publication and post-incident findings are not complete.**

### A hypothetical example: a customer with USDC on an L2

Suppose a user holds USDC in a Binance account and wants to withdraw to an address on Base. Binance's update says USDC is among the ten fully backed assets. Its first-phase list also includes **USDC on Base**. Those two statements address **different requirements**: reserve backing and operational availability.

The customer still needs to check the live Base withdrawal status, verify that the destination wallet supports the token and network, and ensure the chosen address and contract are correct. If the route is temporarily delayed, that is not in itself proof that the USDC was stolen, nor does a reserve statement mean the withdrawal has already been processed. A token balance on an exchange is administered through a custodian's systems; a completed self-custody withdrawal requires an actual blockchain transaction and appropriate confirmations.

## Why it matters

The recovery update changes the immediate question from **"How much was affected?"** to **"How reliably can customer balances and access be restored after a large operational failure?"** The distinction matters to traders, long-term holders and any service that depends on a centralized exchange for settlement or liquidity.

First, **customer losses can be financially absorbed without reversing the original hack**. An exchange may substitute its own resources for missing assets while an investigation continues. That is meaningful for customers, but it does not prove the intrusion technique has been eliminated.

Second, **reserve transparency has multiple layers**. Token holdings, proof of inclusion, liabilities, governance, counterparty exposure, security controls and withdrawal throughput are separate tests. Strong performance on one does not automatically satisfy the others.

Third, **withdrawal access is granular**. A user who holds BTC may see availability restored before someone using another chain or thinly traded asset. Similarly, a liquid major token's full backing cannot be extrapolated to every smaller asset in the same account.

Fourth, the case shows the limits of both purely custodial and purely self-custodial narratives. A custodial platform centralizes operational and counterparty risks but may have corporate resources to cover a breach. A self-custody wallet gives its user direct signing control, but exposes that user to key loss, malicious approvals and transfer mistakes. The safer choice depends on the situation and an informed understanding of each model, not a single slogan.

## What crypto users should know

**1. Check a specific token-network pair, not just a headline.** Verify the asset and selected blockchain inside Binance's current withdrawal page and official network-status notices. The staged schedule can change, and a route listed for phase one may still experience delays or additional checks.

**2. Do not send money in order to "unlock" an exchange balance.** A scammer may impersonate Binance support and request a release fee, seed phrase, private key, one-time code or unfamiliar signature. Never share secrets or trust links from unsolicited direct messages. Learn how [seed phrases, private keys and wallet passwords differ](https://wallet.terenval.com/answers/seed-phrase-vs-private-key-vs-wallet-password/).

**3. Check the destination and network carefully.** Before withdrawing, confirm the receiving wallet supports the exact asset, network and any required destination memo/tag. Where sensible and permitted, make a small test transfer. Terenval Answers explains [how to withdraw from an exchange to self-custody](https://wallet.terenval.com/answers/withdraw-crypto-from-exchange-to-self-custody-wallet/) and [how to choose the right blockchain network](https://wallet.terenval.com/answers/how-to-choose-the-correct-network-when-withdrawing-crypto-from-an-exchange/).

**4. Distinguish "submitted," "processing" and "confirmed."** A withdrawal request in an exchange interface is not yet an on-chain settlement. Save the transaction identifier if issued, monitor the appropriate explorer and contact official support if a withdrawal remains pending. See Terenval's [pending-withdrawal troubleshooting guide](https://wallet.terenval.com/answers/what-to-do-when-a-crypto-exchange-withdrawal-is-stuck-or-pending/).

**5. Verify reserve evidence on the relevant date.** Look at the source, snapshot time, token coverage, whether the complete cryptographic proof has been published and whether a customer-verification function is available. Avoid confusing a new claim about 95% replacement with the older October 31 snapshot.

**6. Protect any self-custody backup.** A blockchain withdrawal does not automatically make an account safe if its recovery phrase has been exposed. Store backups securely and understand [how recovery phrases restore access](https://wallet.terenval.com/answers/what-is-a-seed-phrase-and-how-does-it-restore-a-wallet/). Do not enter recovery words into a website claiming to expedite a Binance refund.

**7. Retain accurate records.** Keep relevant account statements, official notices, support case numbers, withdrawal timestamps and transaction IDs. Rapidly changing incident estimates are not substitutes for evidence about your particular assets.

### Terenval's four-check user recovery checklist

Before interpreting the incident as resolved for an individual account, ask four precise questions:

- **Backing:** Does credible, date-specific evidence cover the exact asset owed to the user?
- **Access:** Is the exact withdrawal network live for this account, and has a test or actual transfer settled?
- **Security:** Have official updates addressed operational controls, and what remains unknown in the post-incident investigation?
- **Continuity:** Can the user reliably access records, support and the destination wallet without exposing sensitive recovery credentials?

A positive answer to only the first question is not enough to establish full recovery for that user. This checklist is editorial guidance, not a certification or claim of independent Binance audit.

## Impact on Bitcoin, Ethereum, Layer 2 and DeFi

### Bitcoin

Bitcoin was one of the first withdrawal routes scheduled to return, with [AFP confirming that the BTC-network phase had begun](https://www.afp.com/en/binance-says-resuming-withdrawals-after-major-hack). Binance's custody incident does **not** indicate that Bitcoin's consensus rules or ordinary self-custody keys were compromised. For customers, the relevant questions are whether BTC withdrawals work, what fees apply and when a transaction receives network confirmations.

### Ethereum and ERC-20 tokens

Binance listed ETH, USDT and USDC on Ethereum for its first phase. The presence of ETH or a stablecoin balance inside an exchange account does not by itself establish that an ERC-20 withdrawal transaction has been created. Verify the destination chain and contract, particularly when the same token symbol appears on multiple networks. The security incident concerned exchange-controlled infrastructure; it should not be confused with a demonstrated break in Ethereum consensus.

### Layer 2 networks and bridges

Arbitrum, Base and Optimism appeared on Binance's first-phase list with specific supported assets. The fact that an asset is fully backed on Binance is **not** sufficient to conclude that all chains offering that asset are open. Deposit, withdrawal, bridge and rollup availability are separate operational conditions. Users should not switch networks merely because the fee is lower without confirming support at both ends.

### DeFi and stablecoins

Investigators may follow stolen assets through swaps, bridges or DeFi protocols. That tracing does not automatically mean the underlying DeFi platforms were exploited. Certain centrally issued stablecoins can have issuer-controlled freeze functions, which may help contain movements but do not automatically restore ownership. The [Terenval stablecoin glossary](https://wallet.terenval.com/glossary/stablecoin/) explains why price stability and issuer control should not be confused with risk-free custody.

## Frequently asked questions

### Has Binance recovered 95% of the stolen cryptocurrency?

**Not necessarily.** Binance says it **replenished or covered approximately 95%** of the affected asset amount using company and designated resources. This is not the same as retrieving 95% of the originally stolen tokens from attackers.

### Are Binance withdrawals working again on November 1, 2026?

**Some began reopening in phases.** Binance announced a first window between **06:00 and 09:00 UTC**, with BTC among the first routes restored. A token or network not yet available may require additional security checks. Always check current status in your own account.

### Can I withdraw USDT or USDC on any blockchain now?

**No universal availability is established.** Binance specified particular token-network combinations for phase one. Check whether USDT or USDC is offered on the **exact chain** you want to use, and confirm the destination supports that chain.

### Does 100% backing of BTC and ETH mean every Binance token is fully covered?

**No.** Binance reports full backing for ten named major assets, while it describes an aggregate **95%** replenishment rate across affected assets. Other, less-liquid tokens make up the remaining gap.

### Is Binance's new proof of reserves the same as an independent audit?

**No.** The October 31 PoR snapshot is point-in-time evidence with specified cryptographic verification methods. It does not, by itself, establish complete corporate solvency, disclose every possible liability or prove that all withdrawals work.

### Has the full zero-knowledge proof been published?

The October 31 Binance update **expected completion around November 3**. At this article's information cutoff, that future milestone had not been independently verified as complete. Check Binance's official PoR portal for the current result.

### Does a frozen stolen token mean Binance has received it back?

**No.** Freezing may immobilize assets at an address without restoring ownership or giving Binance control. Freezing, seizure, recovery and replacement are separate steps.

### Has Binance published the final explanation of the hack?

**Not in the official updates reviewed here.** Binance says it is investigating and plans a post-incident report. Preliminary indications should not be presented as proven root cause.

### Did the Binance incident compromise Bitcoin or Ethereum themselves?

There is **no evidence in the cited official incident updates** that Bitcoin or Ethereum consensus was broken. The report concerns exchange-controlled wallet and operational infrastructure.

### What should I do if my withdrawal remains pending?

Check Binance's current network notice and authenticated account status, then look for a transaction ID. Do not repeat requests blindly or use third-party recovery sites. Retain the reference details and follow [Terenval's guide to stuck exchange withdrawals](https://wallet.terenval.com/answers/what-to-do-when-a-crypto-exchange-withdrawal-is-stuck-or-pending/) as general educational guidance.

## What remains unconfirmed

The final **5%** of affected assets had not yet been reported as fully replenished in Binance's November 1 update. The complete zero-knowledge proof for the October 31 snapshot was expected later, while the final post-incident investigation and independent full-scope assessment remained unavailable in the reviewed official statements. The precise service availability for each user, token and network can change after this article's information cutoff.

Separate reports have attributed the attack to **North Korea-linked TraderTraitor**. [Reuters](https://www.reuters.com/legal/government/binance-resume-withdrawals-after-recovering-bulk-6-billion-stolen-funds-2026-11-01/) and [AFP](https://www.afp.com/en/binance-says-resuming-withdrawals-after-major-hack) reported attribution by the FBI. That is an attribution by investigators; it does not replace a completed public technical root-cause report from Binance or determine the amount eventually recovered.

## Related content suggestions

To understand why a user can have a balance at an exchange while being temporarily unable to transfer it, see Terenval's [custodial versus non-custodial wallet comparison](https://wallet.terenval.com/answers/custodial-vs-non-custodial-wallets/). For practical network checks, use the [exchange-to-self-custody withdrawal guide](https://wallet.terenval.com/answers/withdraw-crypto-from-exchange-to-self-custody-wallet/) and [correct withdrawal network explainer](https://wallet.terenval.com/answers/how-to-choose-the-correct-network-when-withdrawing-crypto-from-an-exchange/). For the incident's earlier stage, read Terenval's [October 30 coverage of the original security breach](https://wallet.terenval.com/news/binance-6-3-billion-security-incident-withdrawals-suspended-2026-10-30/).

An appropriate future news update would verify when Binance reports **100% asset replacement**, publishes the complete **November 3 proof**, releases its **technical post-mortem**, and restores or changes the status of the remaining withdrawal routes. Such milestones should be assessed individually rather than bundled into a single claim that the incident is over.

## Sources

1. **Binance Support, November 1, 2026 — Recovery Update #4.** Original network-by-network phase-one withdrawal list, first-phase window, 95% replenishment statement and remaining 5% caveat. https://www.binance.com/en-GB/support/announcement/security-incident-recovery-update-4-withdrawals-resume-in-phases-2026-11-01-73911fb819b240f88b88256bdd318eda
2. **Binance Support, October 31, 2026 — Recovery Update #3.** 90% reported replenishment, ten named backed assets, reserve funding mechanisms, 00:00 UTC PoR snapshot and estimated November 3 proof. https://www.binance.com/en-GB/support/announcement/security-incident-recovery-update-3-90-of-stolen-assets-replenished-proof-of-reserves-snapshot-provided-2026-10-31-1fdf1f61559c401da0435895ffcccb62
3. **Binance Support, October 30, 2026 — Security Incident Update #2.** Reported incident time, approximately $6.3 billion in affected assets, approximately $3 billion frozen and initial response. https://www.binance.com/en-GB/support/announcement/security-incident-update-2-2026-10-30-d3306d9dca5243548c813b605e1d1751
4. **Reuters, November 1, 2026 — Binance to Resume Withdrawals After Covering Bulk of Stolen Assets.** Independent reporting on the 95% figure, withdrawal schedule and investigative attribution. https://www.reuters.com/legal/government/binance-resume-withdrawals-after-recovering-bulk-6-billion-stolen-funds-2026-11-01/
5. **AFP, November 1, 2026 — Binance Says It Is Resuming Withdrawals After Major Hack.** Independent confirmation of the beginning of Bitcoin withdrawals. https://www.afp.com/en/binance-says-resuming-withdrawals-after-major-hack
6. **CoinDesk, November 1, 2026 — Binance Opens Withdrawals in Phases, Starting With Bitcoin.** Operational reporting on the phased reopening and assets listed for initial access. https://www.coindesk.com/markets/2026/11/01/binance-opens-crypto-withdrawals-in-phases-starting-with-bitcoin-following-usd6-3-billion-hack
7. **Binance — Proof of Reserves.** Description of the exchange's reserve methodology, Merkle-tree checks and zero-knowledge proofs. https://www.binance.com/en/proof-of-reserves
8. **Binance Support — How to Verify Your Account Balance.** Instructions for user verification of PoR data and published proof cycles. https://www.binance.com/en/support/faq/detail/815b25f0cb054bdd9d35eccc408fe981

## Editorial context

**Information cutoff: November 1, 2026, approximately 11:00 UTC.** This article updates previously published coverage of the **October 29 Binance security incident**; it is not a report of a second hack. The headline **95%** is the exchange's reported replacement/coverage ratio in Recovery Update #4, not a forensic finding that 95% of stolen assets were returned. The earlier **90%** figure remains relevant to the chronology and to the retained article slug. The approximately **$6.3 billion** incident estimate, ten fully backed asset categories, remaining 5%, reserve-funding descriptions and phased reopening schedule are attributed to Binance. AFP and CoinDesk independently reported the beginning of Bitcoin withdrawals. The article makes no claim that every withdrawal route is currently open, that all corporate liabilities have been audited or that the technical investigation is complete. Terenval's Three-Ledger Recovery Model and verification checklist are original editorial analysis, not external assurance or formal Binance certifications. This is neutral news and educational context, not an endorsement of Binance or individualized financial, legal or investment advice. Promotional Terenval Wallet material is separate from these conclusions.

## Editorial & technical review

- Published by: Adrian Vance
- Editorial standards and corrections: https://wallet.terenval.com/newsroom/
- Last reviewed: 2026-11-01T12:13:28Z

## Sources

- [Binance Support — Recovery Update #4: Withdrawals Resume in Phases](https://www.binance.com/en-GB/support/announcement/security-incident-recovery-update-4-withdrawals-resume-in-phases-2026-11-01-73911fb819b240f88b88256bdd318eda)
- [Binance Support — Recovery Update #3: 90% Replenished and Proof-of-Reserves Snapshot](https://www.binance.com/en-GB/support/announcement/security-incident-recovery-update-3-90-of-stolen-assets-replenished-proof-of-reserves-snapshot-provided-2026-10-31-1fdf1f61559c401da0435895ffcccb62)
- [Binance Support — Security Incident Update #2](https://www.binance.com/en-GB/support/announcement/security-incident-update-2-2026-10-30-d3306d9dca5243548c813b605e1d1751)
- [Reuters — Binance to Resume Withdrawals After Covering 95% of Stolen Assets](https://www.reuters.com/legal/government/binance-resume-withdrawals-after-recovering-bulk-6-billion-stolen-funds-2026-11-01/)
- [AFP — Binance Says It Is Resuming Withdrawals After Major Hack](https://www.afp.com/en/binance-says-resuming-withdrawals-after-major-hack)
- [CoinDesk — Binance Opens Crypto Withdrawals in Phases, Starting With Bitcoin](https://www.coindesk.com/markets/2026/11/01/binance-opens-crypto-withdrawals-in-phases-starting-with-bitcoin-following-usd6-3-billion-hack)
- [Binance — Proof of Reserves: Merkle Tree and zk-SNARK Verification](https://www.binance.com/en/proof-of-reserves)
- [Binance Support — How to Verify Your Account Balance](https://www.binance.com/en/support/faq/detail/815b25f0cb054bdd9d35eccc408fe981)

Official article: https://wallet.terenval.com/news/binance-replenishes-90-percent-reserves-withdrawals-november-2026/

[Machine-oriented Terenval index](https://wallet.terenval.com/llms.txt)
