Binance Reopens Withdrawals After $6.3B Hack11 min read2,253 words

Binance Reopens Withdrawals After $6.3B Hack

Binance has reopened withdrawals after a reported $6.3 billion hack. See how it is covering losses, what reserve proofs show and what remains unresolved.

Binance hackBinance withdrawalscrypto exchange securityproof of reservescrypto regulation
Binance Reopens Withdrawals After $6.3B Hack

Binance Reopens Withdrawals, but the Hack Recovery Is Not Over

Binance has restarted customer withdrawals after a reported $6.3 billion theft from its hot wallets, reopening access in stages across 15 networks. For users, this is the first practical sign that funds can move again. But reopening isn't the same thing as finishing the recovery - or explaining how the breach happened in the first place.

Binance says it has covered 95% of the impacted amount using company resources, and it plans to fund the remaining 5%. It also published a proof-of-reserves snapshot and says users can verify balances for several major assets. Still, a large share of the stolen funds hasn't been recovered, investigations are ongoing, and the exchange has not yet released a full post-mortem.

This article breaks down what the withdrawal data does - and doesn't - show, how Binance says it is replacing the missing assets, what reserve verification can realistically confirm, and which questions customers (and the wider crypto market) still care about.

What happened when Binance reopened withdrawals?

Binance began restoring withdrawals on Sunday, four days after hackers reportedly drained about $6.3 billion from its hot wallets. The exchange rolled out access in stages, starting with Bitcoin at 06:00 UTC and adding 14 other networks over the next several hours.

The supported networks included Ethereum, BNB Smart Chain, Solana, XRP, Dogecoin, Tron, Polygon, Avalanche, Arbitrum, Base, Optimism, Zcash, TON and Sui. Deposits stayed open during the rollout. Binance also warned that temporary delays could happen as activity picked up.

Why a phased reopening matters

Restarting withdrawals in stages is a practical way to reduce operational risk. An exchange needs to verify that withdrawal systems, wallet balances, signing processes and network connections are working before it flips every route back on. If something is misconfigured, starting with a smaller set of networks can limit the damage.

But that doesn't prove the underlying security issue is fixed. It only shows Binance could process withdrawals again under the conditions of that staged restart. Customers still need separate evidence about what failed, what was exploited, and what controls were changed after the incident.

There's a real difference between two questions for users:

  • Can I withdraw now? Binance's staged reopening answers this for supported networks, with the usual caveat that delays can occur.
  • Is the platform secure and fully solvent? That needs more than a working withdrawal window. Users need clear accounting, security findings, and ongoing monitoring.

What the first withdrawal window showed

Between 06:00 and 15:30 UTC, Binance reportedly processed about $4.65 billion in withdrawals and $1.01 billion in deposits - net outflows of roughly $3.64 billion. Compared with the $171 billion in assets shown in its late-October proof-of-reserves snapshot, that net outflow is about 2.1%.

In raw dollars, that's a lot. In percentage terms, it's a useful check for scale relative to Binance's reported asset base. The figures also suggest users acted during the window while deposits continued. What they don't tell you by themselves is whether users were moving funds permanently, shifting between wallets, or responding to short-term uncertainty.

The practical takeaway: the restart reduced immediate access risk for customers, but it didn't settle the bigger questions about how the theft happened or whether the recovery controls are strong enough over the long run.

How is Binance covering the reported losses?

Binance says it has used company resources to replace stolen assets. In an earlier recovery update, it said it replenished 90% of the impacted amount. That update listed funding sources including part of the Secure Asset Fund for Users, part of its futures insurance fund, and its corporate treasury.

In its Sunday update, Binance said coverage reached 95%. The remaining 5% involves less liquid tokens outside the top ten assets on its proof-of-reserves list. Binance says acquiring those tokens in the needed quantities takes more time, and it is working with industry partners and over-the-counter desks to source them.

Replacing assets is different from recovering stolen funds

These are closely related, but they're not the same thing.

  • Replacing the shortfall means making sure customer liabilities can be met using available assets.
  • Recovering the stolen funds means tracing, freezing, or otherwise regaining control of assets taken by the attackers.

An exchange can cover customer balances from its own resources even if it can't recover every stolen token. That can protect users from taking the direct financial hit - exactly what Binance says it intends to do. But it doesn't make the theft irrelevant, and it doesn't remove the need to explain how the breach happened.

This also matters for how people interpret the recovery numbers. Saying that 95% of the "impacted amount" is covered doesn't automatically mean 95% of the stolen tokens have been recovered. Binance's updates focus on replacement, while investigations continue to track what attackers took.

The trade-off in using internal funds

Using an insurance fund and corporate treasury can help restore confidence faster and reduce the pressure to wait for law enforcement recoveries. But it also shifts where the risk sits: those funds may be treated as a regulatory or liquidity requirement that needs scrutiny after the fact. Binance described the remaining futures fund balance as a regulatory requirement, which is exactly why customers should care what's left in it.

Customers and market observers should press for straightforward answers: Which resources were used? What balances remain in the relevant funds? How will Binance meet any applicable obligations? And what happens if the remaining tokens take longer than expected to source?

Binance says it will cover the full amount and that customers won't bear the financial impact. That promise matters, but a real assessment still depends on evidence that replacement assets are in place - and that other obligations aren't left underfunded.

What do the withdrawal figures and reserve proofs show?

Binance published a proof-of-reserves snapshot dated October 31, which serves as the reference point for the assets included in that report. On Monday, Binance said the full zero-knowledge proof for that snapshot was complete. Users holding BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD or ZEC can use Binance's open-source verifier to check whether their balances are backed at least 1:1.

The exchange said it planned another snapshot covering more tokens on November 4. Binance expected generating the proof to take 40 to 50 hours. The timeline underscores a basic reality: cryptographic verification can improve transparency, but it isn't instant - and a snapshot still reflects a specific moment, not every moment.

What a proof of reserves can verify

A proof of reserves can help users check whether an exchange holds assets that correspond to customer balances included in a specific snapshot. Zero-knowledge approaches can also allow users to verify inclusion without publishing every customer's account details publicly.

That said, proof of reserves has a defined scope. A snapshot is a point-in-time view, not a continuous guarantee. It also doesn't automatically cover the full picture of liabilities, off-chain obligations, internal control quality, or the security of the wallet infrastructure.

So it's fair to say: proof of reserves is one part of assurance, not a complete audit of the business. Users should look closely at which tokens and accounts are covered, when the data was recorded, and what the verification method does - and doesn't - confirm.

What the withdrawal numbers cannot prove

Processing billions of dollars in net outflows shows the withdrawal system handled heavy demand during the reported window. It isn't proof that all stolen assets are fully recoverable, that every customer's experience would be the same, or that the platform could handle every stress scenario.

Likewise, a net outflow of 2.1% of reported reserves doesn't automatically mean the remaining assets were freely available to cover any obligation. Composition, liquidity, liabilities, and timing all matter. A headline total can hide whether certain tokens are harder to source or move - which is relevant given Binance's claim that the uncovered amount is concentrated in less liquid assets.

For customers, the sensible way to read these disclosures is as separate pieces of evidence with separate purposes: withdrawal data speaks to operational capacity during a particular window; reserve proofs relate to covered balances at a specific snapshot; and a post-mortem should explain the security failure and response.

What remains unresolved after the reopening?

The most important unanswered question is how attackers gained access and moved the funds. Binance initially attributed the compromise to an engineer's laptop, then later said it had identified additional breach points. The exchange still hasn't published a full post-mortem explaining how the attackers prepared the operation, which systems were affected, or how the incident was contained.

That detail matters beyond technical completeness. Without a clear timeline and a direct description of the controls involved, users can't tell whether the fixes address the real failure - or only the first problem that was discovered. Other exchanges and custodians also don't get much from an explanation that stays too general.

The stolen funds and law-enforcement response

The FBI has attributed the attack to North Korea, according to the source material. The U.S. Secret Service is working with Circle to trace and freeze funds. Tether reported about $1.57 billion in USDT frozen, while Circle said it had frozen more than $800 million in USDC in coordination with authorities.

These numbers describe reported freezes, not necessarily what ultimately gets returned to Binance or customers. Roughly $3.3 billion in funds that were not frozen hasn't been fully explained, and Binance hasn't laid out how much it expects to recover from that remaining pool. Investigators are continuing to follow wallet activity across ten blockchains.

Tracing across chains and coordinating with stablecoin issuers and law enforcement can help identify freeze opportunities - but it doesn't guarantee recovery. The more the funds move through multiple wallets and networks, the more complex the investigation becomes. A final accounting will need to separate funds frozen, funds recovered, what's still traceable, and what's effectively lost.

What the incident may mean for markets and regulation

The breach triggered a sharp market reaction. Bitcoin reportedly fell about 5% to below $77,000 in the hours after the attack. Shares of Coinbase, Robinhood, Strategy and Strive also declined as investors weighed the possibility of exchange-level losses across the sector.

This reaction reflects a broader concern: users depend on centralized platforms for custody, trading and access to liquidity, and those platforms concentrate operational and security risk. When a major exchange gets disrupted, the impact can spill beyond its own customer base into the wider infrastructure other firms rely on.

For regulators, the incident points back to familiar - but practical - issues: custody controls, incident reporting, reserve transparency, and how insurance or customer-protection funds are used. The information needed to answer those questions isn't all public yet. Until Binance publishes its post-mortem and a more complete recovery accounting, any conclusions about the cause, the response, and regulatory implications should be considered provisional.

Conclusion

Binance's staged reopening restored withdrawal access and put its recovery effort to a real operational test. The reported outflows were significant, though Binance says they were manageable relative to its stated asset base - and that it has replaced 95% of the impacted amount. Its proof-of-reserves work also gives customers a way to verify certain balances at a specific snapshot.

Still, the incident isn't over. The remaining tokens have to be sourced, stolen funds remain under investigation, and the full breach mechanism hasn't been explained. For customers, the next evidence that matters most isn't another headline percentage - it's a complete post-mortem, a clear breakdown of replacement and recovery funds, and ongoing disclosures showing what changed after the attack.

Frequently Asked Questions

Binance began reopening withdrawals in stages, starting with Bitcoin and expanding to 15 networks. The exchange warned that temporary delays could occur during the initial surge in activity. Availability may depend on the asset and network, so customers should check the current status inside Binance before initiating a transaction.
The exchange said it had covered 95% of the impacted amount by Sunday and committed to covering the remaining 5%. That describes Binance’s stated replacement of the shortfall, not necessarily recovery of the stolen tokens. Investigators are still tracking funds, including a reported pool of roughly $3.3 billion that was not frozen.
Not on its own. The proof lets eligible users verify that balances for specified assets were backed at least 1:1 at a particular snapshot. It does not automatically prove continuous solvency, cover every token or liability, or explain the security controls that failed. It is one useful disclosure within a broader assessment.
The source material says the FBI attributed the attack to North Korea. The U.S. Secret Service is also working with Circle to trace and freeze funds. These are law-enforcement actions and attributions; a full public account of the attack’s methods and timeline has not yet been provided by Binance.

Related articles