Binance Hack: 90% of Stolen Assets Replenished
Binance says it has replaced 90% of assets stolen in its $6.3 billion hack. Learn what the update confirms, what remains unverified, and what comes next.

Binance Says It Replaced 90% of Assets After $6.3B Hack
Binance says it has replenished 90% of the assets stolen in its $6.3 billion hack and is targeting Sunday to resume withdrawals. The update matters for customers who are waiting to move funds. But the wording still leaves key questions open: what "replenished" means, where the replacement assets are coming from, and what customers can actually verify on their own.
Binance says it's using money from its corporate treasury, a portion of its Secure Asset Fund for Users (SAFU), and part of its futures insurance fund to replace what was stolen. It also says customer balances in Bitcoin, Ether, and eight other assets are fully backed. The remaining gap, Binance says, involves less-liquid tokens that it is still buying.
These statements outline a plan and where Binance says it stands right now - not a completed independent audit. Binance has published a new reserves snapshot, but says its full cryptographic proof is still being generated. Below is what Binance has reported, what remains unclear, and what Sunday's withdrawal target means for users and the wider market.
What does Binance mean by replenishing 90% of the stolen assets?
Binance says it has replaced 90% of the stolen assets, up from 80% the previous day. It's worth keeping the terms straight: replacing stolen tokens is different from recovering stolen tokens.
When Binance says it has replenished 90%, it generally means it is acquiring or allocating assets to cover what customers were short. That doesn't automatically mean Binance has found and regained the cryptocurrency taken in the hack.
Binance hasn't laid out how much of the stolen crypto has been recovered. Until it provides a separate accounting, customers shouldn't treat "90% replenished" as the same thing as "90% of the stolen assets recovered."
Binance says balances in BTC, ETH, and eight other assets are fully backed. It says the remaining shortfall is tied to less-liquid tokens, which it's still buying through market trades and over-the-counter transactions. That can take longer than replacing highly liquid assets - less liquidity can mean fewer options at a given price, and large purchases can affect how trades get executed.
Why the percentage needs context
A single percentage doesn't tell you how the shortfall breaks down by token. Even if the overall figure is "90%," a bigger share of the remaining 10% could be concentrated in specific assets - especially if those assets are harder to source. In the update, Binance doesn't provide the remaining quantities, token-by-token values, or the prices used to compute the replenishment number.
That doesn't prove Binance is wrong. It just means outside readers can't easily check the claim without a detailed breakdown. For customers, the practical question is whether your specific assets are fully backed and whether withdrawals for them are available - and what evidence supports that.
Key takeaways:
- Binance's 90% figure refers to assets it says it has replaced, not necessarily assets recovered from the hackers.
- The exchange says BTC, ETH, and eight other assets are fully backed.
- Less-liquid tokens make up the remainder of the reported shortfall.
- The public update doesn't include a complete token-by-token accounting.
How is Binance funding the replacement assets?
Binance says it's funding the replacement using three sources: its corporate treasury, a partial deployment of SAFU, and a portion of its futures insurance fund. It says it will absorb the financial impact rather than pass the loss onto users. It also says the futures insurance fund will remain above required risk-management levels.
The issue is that the details are still incomplete. Binance hasn't said how much each source contributes, or what the futures insurance fund's minimum required balance is. Without those numbers, customers can't independently assess how large a draw each pool takes or how the remaining balance compares to the stated risk threshold.
Binance previously said it had set aside $6.34 billion to cover losses, including $5 billion in the affected cryptocurrencies. That figure isn't a simple breakdown of "new cash" sitting somewhere, or a measure of what's been recovered or freely available. It's a provision for losses, while the latest update describes progress replacing assets. Related disclosures, but not the same metric.
Frozen assets are not the same as replacement assets
After the hack, industry partners including Tether and Circle froze about $3 billion in affected assets, according to the report. Those frozen funds are separate from Binance's replacement of stolen tokens.
A freeze can stop certain assets from moving, but it doesn't automatically mean those funds get returned to Binance - or that Binance has matched customer balances using the frozen assets.
This matters when you see large numbers tied to the incident. A headline amount might refer to estimated theft, funds set aside by Binance, assets frozen by third parties, or tokens purchased as replacements. Each is describing a different part of the response. Without clear accounting, it's easy to end up with a picture that looks more settled than the public evidence supports.
For customers and market observers, the most useful next disclosure would separate: the loss estimate, the value and source of replacement assets, any crypto actually recovered, and how much is frozen by other issuers. Until then, treat those totals as separate figures with separate meanings.
What is verified, and what remains uncertain?
Right now, most of the information comes from Binance's own updates and statements. Binance has published a new reserves snapshot and says it's generating a full zero-knowledge proof. Binance says that process takes about 40 to 50 hours, due to the computing workload. A snapshot is a step toward transparency, but it isn't the same as having the complete cryptographic proof available for review.
Timing is also part of the uncertainty. CertiK said it needed more information to verify Binance's claimed $5 billion in replacement cryptocurrencies. That comment came before Binance published the new reserves snapshot. The snapshot adds some context, but Binance's own update says the full proof is still in progress. So the most defensible reading is not "the claims are disproven," and not "everything has already been independently confirmed."
What the public update does and does not establish
Based on Binance's reported statements, it says:
- It has replenished 90% of the stolen assets.
- Customer balances in 10 named asset categories - BTC, ETH, and eight others - are fully backed.
- It plans to use company and fund resources to absorb the loss.
- It's targeting Sunday to resume withdrawals.
Some details are still missing:
- How much each funding source (treasury, SAFU, futures insurance) contributes.
- The minimum required balance for the futures insurance fund and what it will be after use.
- A token-by-token account of the remaining shortfall.
- How much crypto has actually been recovered from the attackers.
- The completed cryptographic proof supporting the reserves and replacement claims.
The incident has also been attributed by TRM Labs to North Korea's TraderTraitor group. That's an attribution reported by TRM Labs, not a substitute for Binance's accounting or a public technical investigation. Attribution, recovery, and customer solvency are separate questions - evidence for one doesn't automatically answer the others.
In practice, confidence grows when claims line up with evidence over time. A reserve snapshot, a completed proof, working withdrawals, and a clear accounting answer different questions. Customers shouldn't treat any one of those as a total replacement for the others.
What does the Sunday withdrawal target mean for users?
Binance says it remains on track to resume withdrawals Sunday. That's a target, not a promise that every withdrawal route, asset, and account will restart at the same time.
The report doesn't specify a precise restart time, whether withdrawals come back in stages, or whether specific limits apply to particular tokens.
For users, the distinction is simple even if the situation isn't. An exchange can say balances are backed while withdrawals are still temporarily unavailable. "Backed" refers to what the exchange says it holds or has allocated. "Withdrawals available" is about whether customers can move those assets through the platform right now. Closely related, but not identical.
If you hold assets on Binance, rely on the exchange's official status updates for the availability of your specific asset. Check the supported withdrawal network and any announced limits before initiating a transfer. During a restart, don't assume that one successful withdrawal proves every asset and network is working normally. Likewise, a delay affecting one token doesn't automatically mean every customer balance is impaired.
How to assess the update without overreacting
In the first hours after an exchange incident, people tend to make two mistakes. One is treating the headline "recovery" percentage as proof the risk is over. The other is interpreting every operational delay as evidence of insolvency. Neither conclusion follows from the reported facts by itself.
A more useful approach is to watch a short set of observable milestones:
- Withdrawals resume: Can customers withdraw, and are there asset-specific restrictions?
- The proof is published: Does the completed cryptographic evidence support Binance's reserve claims?
- The shortfall is accounted for: Does Binance identify the remaining less-liquid tokens and explain how it will acquire them?
- Funding is explained: Does the exchange clarify how it's using its treasury and funds, including the insurance fund's remaining position?
- Recovery is reported separately: Does Binance clearly distinguish recovered funds from assets it replaced?
This is more helpful than treating "withdrawals open" as the end of the story. The restart would be an operational milestone. The accounting and proof would determine how much confidence the public can place in the broader claims.
Conclusion
Binance's reported 90% replenishment is progress, but it isn't the same as recovering the stolen crypto or completing independent verification. Binance says major assets are fully backed, the remaining gap involves less-liquid tokens, and it's targeting Sunday for withdrawals. The next useful proof will be the completed cryptographic evidence, clearer funding details, and a token-level accounting of the remaining shortfall. Until those arrive, treat the update as a significant company-reported step - not the final accounting for a $6.3 billion hack.