Binance security incident: $6.3 billion preliminary impact, withdrawals still paused

Binance disclosed a security incident involving unauthorized withdrawals on 29–30 October. In its 30 October notice, the exchange estimated the total impact at about $6.3 billion and said approximately $3 billion in affected assets had been frozen on-chain with partners. Both are company figures at that point in time. Neither establishes the final net loss: frozen assets are not necessarily recovered, returned or reimbursed.

Service status and separate entities

Binance says it revoked the affected address authorization, contacted law enforcement and blockchain investigators, and initially halted deposits and withdrawals for checks. Its later official update said deposits were operating again, while withdrawals remained paused for security work on the withdrawal system and related addresses. A return within 48 hours was the company's expectation, not a guaranteed deadline. Binance Japan separately said it found no impact on assets held in its own cold wallets, although it temporarily stopped crypto withdrawals as a precaution. Customers must check the current notice for their own contracting entity and jurisdiction.

The cause and loss remain under investigation

Binance's initial inquiry suggested a compromised DevOps engineer's laptop might have enabled access to a service container and unauthorized withdrawal requests. It said it had found no evidence of wallet private-key leakage and would publish a technical post-mortem. A subsequent update described multiple factors and further tracing of the attack path. The laptop should not be presented as the settled, sole cause; third-party attribution of an attacker is not a law-enforcement or judicial finding.

Binance promises to cover all losses from its SAFU fund and company resources and to update its Proof of Reserves after remediation. These are company commitments, not evidence that every affected customer has already been paid. Abu Dhabi Global Market's Financial Services Regulatory Authority says it is engaging with Binance and monitoring the incident; it did not certify the loss estimate or compensation.

Why it matters

Paused withdrawals can disrupt collateral movements and cross-platform settlement even when deposits and trading are available. Customers should check official in-app or directly entered website notices, verify their legal counterparty, preserve balance and withdrawal records, and beware of fake recovery messages. TraderVote's assessment: the decisive follow-up is the technical post-mortem, disposition of frozen assets, final net loss, customer-by-customer redress and withdrawal restoration across legal entities—not a ranking of headline theft figures.

Sources: [Binance incident notice, 30 October 2026](https://www.binance.com/en/support/announcement/detail/c5a8729a97ac486d963784d96c5642d7); [Binance service update, 30 October 2026](https://www.binance.com/en/square/post/10-30-2026-binance-deposits-are-no-longer-affected-pledges-to-cover-losses-related-to-the-incident-382683663031259); [FSRA statement, 30 October 2026](https://www.adgm.com/media/announcements/fsra-statement-regarding-security-incident-involving-binance); [Binance Japan notice, 30 October 2026](https://www.binance.com/en-JP/support/announcement/detail/062daeb5a08b444ca5248113154457ae); [Associated Press, 30 October 2026](https://apnews.com/article/binance-cryptocurrency-security-hack-north-korea-550e9b876550f71f07098494fe735beb). Accessed 30 October 2026, Los Angeles time. Service status may change after filing. The cover is conceptual editorial art, not actual incident equipment.

This article is not investment advice.