Binance Breach: Withdrawals Resume After $6.3B Theft
Binance has resumed withdrawals in phases after a $6.3 billion crypto theft. See what its 95% coverage claim and $3.6 billion net outflow mean.

Binance Reopens Withdrawals After a $6.3 Billion Breach. What Changes Now?
Binance has started restoring withdrawals after it froze deposits and withdrawals following a reported $6.3 billion cryptocurrency theft. The exchange says it has covered 95% of the stolen assets and will take the financial hit rather than push losses onto users. Still, reopening isn't the same thing as a full recovery. Binance says it's still tracking down the remaining affected assets, and some networks and services are staying restricted.
The initial withdrawal window also showed how quickly users acted. Binance reported processing $4.6 billion in withdrawals and $1.0 billion in deposits between 6:00 a.m. and 3:30 p.m. Coordinated Universal Time, for a net outflow of $3.6 billion, or 2.1% of its assets under management. Those numbers help, but they don't answer the big open questions about what caused the breach, how recovery is proceeding, or what safeguards will hold up over the long run.
This article separates what Binance and the FBI say from what hasn't been explained yet. It breaks down how phased withdrawals work, what the reported figures do and don't tell users, and which details are likely to matter in the investigation's final account.
What happened in the Binance breach
Binance says hackers stole $6.3 billion worth of cryptocurrency from its wallets. In response, the exchange froze deposits and withdrawals while its teams worked to contain the incident, assess what was affected, bring services back online, and complete security checks. Binance framed the freeze as temporary - part of the containment process - not a permanent shutdown.
The FBI attributed the breach to TraderTraitor, a North Korean group. The agency says the group was converting stolen funds mainly into Ethereum, with more laundering likely. Binance has also previously pointed to North Korean actors in similar contexts. Attribution is an important thread, but it doesn't explain how the attackers got in or which specific controls failed.
And that distinction matters. Naming an alleged group answers one question; explaining the attack path answers another. A full technical explanation would need to clarify how attackers reached the compromised wallets, what detection and containment steps kicked in, and how Binance decided it was safe to restart affected services. The information released so far doesn't provide that level of detail.
Why the exchange froze deposits and withdrawals
A withdrawal freeze limits movement of funds while an exchange investigates what happened. Practically, it gives security teams time to identify which systems were affected, verify balances, and confirm that restoring services won't expose users to further losses. It can also stop deposits from landing in parts of the platform that aren't ready yet.
There's a real downside for customers: during a freeze, users can't rely on normal access to funds through the exchange. Binance acknowledged that withdrawal access matters, but said the restriction was necessary while it contained the incident and completed security checks. It's a trade-off that's hard to avoid - reopen too fast and you risk compounding the damage, but leaving things frozen too long can increase uncertainty and disrupt everyone's plans.
What Binance means by covering 95% of the stolen assets
Binance says it has covered 95% of the stolen assets and is still working to source the remaining affected funds. It says the remaining assets are less liquid, making them slower to obtain at the scale required. The company also says it will absorb the financial impact and won't pass losses to users.
That language needs a careful read. "Covered" doesn't automatically mean "recovered from the attackers." Based on what's available here, Binance is describing steps to cover the affected assets and source what remains - but it doesn't explain, in this information, how much was actually retrieved from the attackers or exactly how the coverage is being funded. Those are different measures, and users will want the promised incident report to spell them out clearly.
What phased withdrawals mean for users
Binance says withdrawals will restart in phases, depending on the network and the asset. That means this isn't a single switch that makes everything available at once. In its Sunday morning update, Binance's network status page showed a mix of normal, partially suspended, and fully suspended statuses.
For instance, Bitcoin deposits and withdrawals were listed as partially suspended. Ethereum deposits were listed as normal, while Ethereum withdrawals were still partially suspended. These reflect the service state at that moment, not a guarantee that everything will stay the same as Binance finishes checks and adjusts operations.
Binance also warned that traffic could slow withdrawals and lead to temporary delays. A service can be "open" but still process requests more slowly than usual. If you need to move funds, the practical move is to check the status for the exact asset and network before you submit a transaction - and plan for the possibility that processing won't be immediate.
Why asset-by-asset reopening is more useful than a blanket announcement
A broad message like "withdrawals are back" can't capture what users actually experience when different networks are at different stages. Each asset may depend on different infrastructure and different operational checks. Binance's phased approach makes those differences visible - even if the result is less convenience and more "it depends" for users.
When reading a status page, it helps to separate three questions:
- Is the asset supported for withdrawals right now? A partially suspended status usually means access is limited; it isn't the same as normal operation.
- Which network are you using? Some routes may be open while others are restricted. Confirm the network before you act.
- Will it take longer than usual? Binance has warned of delays, so timing may differ even when withdrawals are available.
These checks are operational, not investment advice. The point is to avoid treating a general reopening headline as confirmation that every transfer route is working normally.
The user-facing trade-off
Phased restarts reduce the pressure to bring everything back before all checks are finished. The trade-off is uneven access - longer processing times in some cases, and changing availability across assets. That uncertainty is frustrating, but it's also more informative than assuming the entire exchange is ready at the same time.
For Binance, the test is whether status updates stay specific and current as conditions change. For customers, the test is whether decisions can be made using up-to-date, asset-level information instead of relying on a headline that suggests the exchange is fully back online.
What the recovery and outflow figures show
Binance reported that between 6:00 a.m. and 3:30 p.m. Coordinated Universal Time it processed $4.6 billion in withdrawals and $1.0 billion in deposits. The difference was a net outflow of $3.6 billion, which Binance said amounted to 2.1% of its total assets under management.
It's worth not mixing these concepts up. The $4.6 billion number is what was withdrawn during the window. The $3.6 billion net outflow accounts for deposits arriving during the same period. Neither number alone shows how many individual customers withdrew, whether outflows stayed high later, or how the exchange's overall asset position changed after that reported interval.
A net outflow also isn't a standalone measure of solvency or security. It describes flows over a particular period, not the full breakdown of assets, liabilities, custody arrangements, or the exchange's ability to meet future obligations. The 2.1% figure provides a scale comparison supplied by Binance, but it doesn't replace detailed accounting or independent verification.
How to interpret the 95% coverage claim alongside withdrawals
The 95% coverage statement and the $3.6 billion net outflow describe different things. The first is about Binance's progress in covering assets tied to the theft. The second is about the difference between deposits and withdrawals during a defined interval after withdrawals resumed. They shouldn't be stitched together into a single "case closed" conclusion.
A more complete read would need at least three clarifications:
- What "covered" means in accounting terms. Is it replaced with other assets, recovered from the attackers, backed by funds elsewhere, or calculated in another way?
- How Binance is sourcing the remaining assets. Binance says they're less liquid and take longer to source at required scale, but the mechanics aren't described in the information available here.
- How the loss affects the exchange's wider position. Binance says users won't bear the loss, but the incident report should explain how that commitment is being carried out.
Until those details are published, the numbers are disclosures - not a full independent assessment. Binance says it will issue a more detailed incident report once the investigation is complete.
Why the first withdrawal window is only a snapshot
The reported period lasted nine and a half hours. It captures the immediate response after withdrawals restarted, when users may have been waiting to move funds and demand for service could have been unusual. It doesn't tell you what users did in the days after, or how quickly processing returned to normal.
To get a sustained view, you'd need more than one interval: repeated flow figures, clear explanations of the denominators, and updates showing whether withdrawals and deposits are operating normally across networks. In other words, the first window is just one data point - and the key question is whether Binance continues to share comparable information as operations stabilize.
What to watch as Binance investigates
Binance says the work is ongoing. It plans to strengthen safeguards, complete the recovery process, and provide further updates. It's also promised a more detailed incident report once the investigation wraps. That report matters more than broad statements because it should lay out what happened, what changed, and whether the response addresses the underlying risks.
The recovery effort has two tracks. One is operational: restore deposits and withdrawals safely across the affected assets and networks. The other is financial and investigative: source the remaining affected assets, determine what can be recovered, and document the incident in a way that holds up under scrutiny. Progress on one track doesn't prove completion of the other. A network can reopen while the investigation still has unanswered technical questions, just as financial commitments can be announced before every detail is explained.
What a useful incident report should explain
A report that helps users and the broader crypto market needs to answer specific questions, not just offer general assurances. Look for:
- Scope: which wallets, systems, assets, and services were affected - and which weren't.
- Timeline: when the compromise was identified, when restrictions were applied, and how the phased restoration decisions were made.
- Attack path: what investigators believe enabled the theft, with clear separation between confirmed findings and open questions.
- Loss accounting: how Binance calculates the $6.3 billion figure and the 95% coverage claim, including whether assets were recovered or replaced.
- User impact: whether any customer balances or services were affected beyond deposit and withdrawal restrictions.
- Control changes: what safeguards were added or modified, and how Binance will test that those changes work.
This isn't asking for every sensitive security detail to be published. Some information can increase risk if it's shared too broadly. But a credible account should explain the control failure and the corrective steps at a level that lets users understand what happened and how Binance responded - without turning the report into guesswork.
What this incident can and cannot tell users about exchange risk
An exchange is both a trading venue and a service provider. Users rely on its custody systems, operational controls, communication practices, and ability to restore services under pressure. This incident makes that dependence visible: customers couldn't withdraw freely during the freeze, and reopening didn't immediately restore every asset route to normal.
But that doesn't prove that all exchanges share the same specific vulnerability. It also doesn't automatically mean Binance's safeguards will fail or succeed. The practical takeaway is narrower: having a balance showing on a platform doesn't equal having uninterrupted control over funds. Users should understand the platform's service and custody risks - especially when disruption quickly turns access into something conditional.
For institutions and other large users, the same principle applies in operational terms. Exposure isn't just the value held on a venue; it also includes how you reconcile balances, make time-sensitive transfers, and handle temporary service restrictions. Those are risk-planning questions - not conclusions you can safely draw from the initial update alone.
Conclusion: reopening is a milestone, not the finish line
Binance's phased restart restores some access after a $6.3 billion theft, and the company says it will absorb the financial impact instead of passing losses to users. Its reported $3.6 billion net outflow offers an early view of customer activity, while the 95% coverage claim points to progress on the affected assets. Neither figure ends the investigation.
The next real test is transparency over time: clear network-level service updates, an explanation of what "covered" means, and an incident report that separates confirmed findings from unresolved questions. For users, check the status of the exact asset and network before transferring and expect delays if traffic is heavy. For the market, treat reopening as an operational milestone - not proof that every financial and security issue has been fully resolved.