Binance Halts Withdrawals as Hackers Suspected of Stealing Billions in Crypto

Binance suspected of cyberattack and suspends withdrawals; external estimates put losses at billions but no official confirmation.
Binance suspended withdrawals Thursday after detecting anomalous activity. Its security team suspects a targeted cyberattack, and some external estimates say hackers stole billions in crypto, but the figure is unconfirmed. The article notes that suspending withdrawals is a common loss-mitigation measure but also amplifies panic and bank-run expectations. Crypto theft losses usually require on-chain tracing, audits, and law enforcement before confirmation, and initial estimates often deviate significantly. The incident again exposes the structural risks of centralized exchange custody, with next steps depending on official explanations, on-chain fund flows, and regulatory intervention.
The world's largest cryptocurrency exchange, Binance, suspended withdrawals on Thursday following a suspected cyberattack, with some estimates claiming hackers stole billions of dollars' worth of crypto assets in the incident. The news spread rapidly across the crypto community and tech media, but so far official disclosures remain limited and the full picture of the event is yet to be clarified.
Incident Recap: Withdrawals Suspended and Attack Suspicions
According to RSS source reports, Binance urgently suspended withdrawals on Thursday after detecting anomalous activity. The security team suspects a targeted cyberattack, and attackers may have already moved large amounts of crypto assets out of exchange wallets. Some estimates describe the scale of losses as being in the "billions of dollars" range, but this figure is currently only external speculation and has not been confirmed by Binance officially.

Suspending withdrawals is a common measure for centralized exchanges responding to security incidents—freezing the flow of funds can both prevent attackers from moving assets further and buy time for forensics and loss mitigation. But this action itself also amplifies market panic: users cannot withdraw their assets in time, which easily triggers expectations of a bank run and in turn affects the platform token and related token prices.
Cold wallets and hot wallets are fundamental concepts for understanding exchange theft incidents. Hot wallets refer to wallets connected to the internet, used for daily deposits, withdrawals, and transaction signing—high liquidity but a large attack surface; cold wallets are solutions that store private keys offline, typically used to hold the majority of user assets on an exchange. Mature exchanges generally adopt an architecture of "most assets in cold storage, a small portion in hot wallets for circulation." Part of the reason for the huge discrepancy in loss estimates in this incident is that outsiders cannot determine whether the stolen funds came from hot wallets or cold wallets—if only hot wallets were compromised, losses are usually manageable; if cold wallets or multi-signature processes were breached, it means more serious internal or supply chain vulnerabilities.
The Uncertainty Behind the Billions-of-Dollars Estimate
The phrase "billions of dollars" deserves cautious treatment. Loss amounts in crypto asset theft cases typically can only be gradually confirmed after on-chain fund tracing, exchange audits, and law enforcement intervention, and initial estimates often overestimate or underestimate. In many historical exchange theft incidents, there were gaps between the initial rumored figures and the final officially announced numbers.
For ordinary users, the most reliable source of information at present remains Binance's official announcements. Until the official side provides a clear loss range, compensation plan, and recovery timeline, any specific figure should be treated as unverified speculation.
On-chain tracing and Proof of Reserves are two key tools for verifying the scale of losses. On-chain analysis firms track the address flows of stolen funds, mixer usage, and cross-chain transfers through public blockchain ledgers, which can provide relatively objective evidence of fund paths, but it is difficult to directly convert this into the platform's actual losses. Proof of Reserves allows exchanges to publicly disclose the correspondence between their address assets and user liabilities, used to prove solvency. However, Proof of Reserves has limitations such as snapshot timing and opaque scope of liabilities, and historically there have been controversies where "the proof was valid but the funds had long been moved," so it is more suitable as cross-validation rather than an absolute guarantee.
The Trust Paradox of Centralized Exchanges
This incident once again exposes the structural risks of centralized exchanges: users entrust assets to the platform in exchange for liquidity and trading convenience, but at the same time completely hand over security responsibility to the platform. Once the platform's defenses are breached, user assets are directly exposed to risk.
As the exchange with the largest global trading volume, Binance's security incidents have impacts far beyond a single platform—they may trigger chain reactions at the regulatory level, drive stricter requirements for Proof of Reserves and separation of cold and hot wallets, and also prompt some users to re-examine the practical significance of the industry saying "Not your keys, not your coins."
"Not your keys, not your coins" originates from the Bitcoin community and emphasizes that only self-custody of private keys counts as truly owning assets. Corresponding to this are self-custodial wallets and the decentralized exchange (DEX) model: users manage their own private keys, transactions are completed on-chain through smart contracts, and the platform does not custody funds. But self-custody also means users must bear the risks of private key loss, phishing attacks, and contract vulnerabilities themselves, and liquidity and fiat on/off-ramp convenience are usually inferior to centralized platforms. This trade-off is precisely the other side of the centralized exchange trust paradox—risk does not disappear, it merely shifts from the platform to the users themselves.
What to Watch Next
The direction of the incident depends on several key milestones: whether Binance can restore withdrawals within a short period and provide a credible incident explanation; whether on-chain analysis firms can trace the flow of stolen funds; and whether regulators will intervene in an investigation. Before information becomes clear, users are advised to keep following official channels and avoid making hasty decisions based on rumors on social media.

Security incidents in the cryptocurrency market have historically had an amplifying effect. The final characterization of this attack and confirmation of losses will become a sample for observing the level of security governance at centralized exchanges.
One-line Summary
Binance suspected of cyberattack and suspends withdrawals; external estimates put losses at billions of dollars but no official confirmation.
Paragraph Summary
Binance suspended withdrawals on Thursday after detecting anomalous activity. Its security team suspects a targeted cyberattack, and some external estimates say hackers stole billions of dollars' worth of crypto assets, but the figure has not been officially confirmed. The article notes that suspending withdrawals is a common loss-mitigation measure for exchanges responding to security incidents, but it also amplifies market panic and triggers expectations of a bank run. Loss amounts in crypto theft cases usually require on-chain tracing, audits, and law enforcement involvement before confirmation, and initial estimates often deviate significantly. The incident once again exposes the structural risks of the centralized exchange custody model, and its subsequent direction depends on the official incident explanation, the on-chain flow of stolen funds, and whether regulators intervene.
Related articles

Will GitHub Die? Open Source Maintainer Burnout and the Collaboration Crisis in the AI Era
Lex Fridman podcast discussion on open source maintainer burnout and GitHub's predicament: massive pull requests overwhelm core maintainers, and AI worsens code bloat. Using math journal peer review and Poincaré conjecture verification as analogies, the article analyzes why verification in knowledge production must be deliberately slow, and how open source communities can avoid the failure mode of maintainers exiting.

Stop Building Cookie-Cutter AI Websites: 3 Tools That Transform Your Coding Agent
Three tools that boost AI coding agents: FFmpeg skill for local video editing in Claude Code and Cursor, Hallmark's 50 design themes to fix cookie-cutter AI sites, and Jailbreaks' 25+ model prompts.

How America's Gerontocracy Squeezes the Younger Generation
Americans over 55 hold nearly three-quarters of national wealth, alongside an 80-year-old president and elderly congressional leaders. The Atlantic's Idrees Kahloon explains how gerontocracy drives up housing costs, squeezes opportunities for the young, and explores zoning reform and child poverty reduction as practical fixes.