Binance hack: What happened and what users should know
Get the latest on the Binance hack, including reported losses, frozen assets, paused services and what the incident means for exchange and DeFi users.

Binance's $5.9 Billion Hack: What We Know So Far
Binance is investigating a major security incident involving assets linked to an Ethereum wallet. Chainalysis estimated that about $5.912 billion in crypto was stolen, while Binance said roughly $3 billion had been frozen as investigators traced funds. Those figures don't line up, and the final loss hasn't been determined yet.
For users, the questions are immediate and practical: Are deposits and withdrawals available? Have customer funds been affected? And what does it really mean when stablecoin issuers and blockchain platforms can freeze assets?
As of October 30, Binance had temporarily suspended deposits and withdrawals while it conducted security checks. Binance said it would cover losses, but it hadn't yet established the full impact on users.
This article separates what's been confirmed from what's still preliminary, explains how the response played out across exchanges and DeFi, and outlines what users and market participants can do while details are still being verified.
What happened in the Binance hack?
The incident started with suspicious transfers from a wallet described as linked to Binance. Blockchain researcher Spreek flagged the activity after assets moved from that wallet to a newly created address via a contract call. Reports said the transaction was funded through Tornado Cash, a privacy protocol. Later reports claimed wallets tied to the activity began selling USDT through decentralized exchanges.
Binance confirmed it was investigating a potential security issue, but at first said it had not verified an impact on user funds. That distinction matters. Unusual onchain activity can point to an exploit, but the transfer itself doesn't fully explain how access was gained, who controlled the addresses, or what Binance's internal accounting will ultimately show.
The suspected signing-system compromise
An early assessment from Blockaid co-founder and CEO Ido Ben-Natan suggested the attacker may have misused transaction-signing infrastructure, rather than simply stealing a private key. In that scenario, an attacker targets the system that approves transactions, tricking it into authorizing malicious transfers without taking the key directly.
This is still an early hypothesis, not a confirmed technical finding. The response could look very different depending on what was actually compromised. A leaked key and a compromised signing workflow call for different controls, investigations, and fixes. Binance said it would publish a post-mortem after the investigation is complete. Until then, claims about the exact attack path should be treated as provisional.
Arkham Intelligence identified wallets labeled binance-hacker-1029 and reported holdings of approximately $5.84 billion. That number reflects the balances shown in those labeled wallets, not a guaranteed "final loss" for every dollar represented there. Wallet labels are just analytical labels. Balances can change as funds move, are sold, or are frozen.
What is confirmed, and what is still unclear?
While investigators looked into the incident, Binance took steps that affected operations. It temporarily suspended withdrawals and then deposits while it ran security checks and coordinated with law enforcement and industry partners. Binance also temporarily suspended Binance Alpha trading. Binance said it would resume withdrawals once the issue was resolved and that it would cover losses.
As of October 30, several core details were still missing from the available updates:
- The exact technical vulnerability or failure that enabled the transfers.
- The final amount of assets that were irretrievably lost, instead of moved or frozen.
- Whether Binance customer balances were affected, and if so, how.
- Whether the attacker still controlled assets that hadn't been frozen.
Binance also said the incident did not affect Binance.US. That's a specific statement about the US platform - so it shouldn't be stretched into a broader conclusion about other services or the overall scope of the investigation.
How much was stolen, and how much was frozen?
Chainalysis put the "stolen" amount at approximately $5.912 billion at the time of theft. Binance, meanwhile, reported that verified frozen assets reached $3 billion by October 30. These numbers are answering different questions: one tries to estimate what was taken, while the other counts assets that have been traced and made inaccessible through coordinated action.
A frozen asset doesn't automatically turn into recovered cash the way people often assume. Frozen funds may sit with an issuer, move through intermediary wallets, or depend on further actions by a protocol or governance process. The final accounting depends on what's verified, what's recoverable, and how each transfer is classified.
Why the reported figures changed
Early public estimates differed. Binance initially cited figures that included about $971 million frozen by Tether and $823 million by Circle. Later statements from those companies pointed to larger totals. Tether's CEO said the company had frozen more than $1.567 billion in USDT tied to the incident, and Circle's CEO said it had frozen more than $800 million in USDC. Binance later reported verified totals of $2.54 billion and then $3 billion.
Those updates shouldn't be treated like a simple running total. Reports came out at different times and may have covered different assets, addresses, or verification stages. The same funds can show up in multiple descriptions as they're traced and moved to addresses that others can control. Binance said its total could still rise as investigators identify more assets.
It also helps to separate four measures people often mix together:
- Wallet balances: assets visible at addresses linked to the incident.
- Estimated stolen value: an analyst estimate of assets taken, often valued at the time of transfer.
- Frozen assets: funds made inaccessible through an issuer, platform, or governance action.
- Recovered funds: assets that are ultimately returned or accounted for after the investigation.
At the time of the latest update, wallet balances, estimated stolen value, and frozen assets were still being investigated. A definitive recovery total wasn't available yet.
What a freeze can and cannot do
Stablecoin issuers have controls that can block certain tokens from being transferred, and that can matter if stolen funds get converted into stablecoins. But freezing isn't a universal undo button. Freezes are usually limited to tokens and addresses within the issuer's control, and they only work once the connected assets are identified.
Other funds can still move across networks, get exchanged for different tokens, or sit in wallets that intermediaries can't access. Even if an asset is frozen, the follow-up question - whether it's held, transferred, or returned - can turn into legal and policy decisions. The $3 billion figure is meaningful, but it doesn't, by itself, prove that the entire amount has been returned to Binance or its users.
How did exchanges, issuers and DeFi protocols respond?
This response went beyond Binance. Stablecoin issuers, blockchain networks, analytics firms, law enforcement, and trading companies all played different roles. Their actions show how quickly coordination can happen during a major incident - and it also highlights why emergency interventions raise questions about control and governance.
Tether, Circle, and Ripple said they were freezing assets linked to the suspected hack or supporting the investigation. World Liberty Financial said it froze $27 million in its USD1 stablecoin and $2 million worth of WLFI, working with BitGo. Ripple's senior vice president of stablecoins said Ripple was actively freezing affected RLUSD holdings but didn't provide a total. Each step applied only to the assets and systems within that organization's reach.
The Arbitrum and Aave actions
Arbitrum's Security Council said it transferred $30.5 million in assets connected to the exploit to an intermediary frozen wallet. It said the original address could no longer access those funds, which could only be moved through additional Security Council action or a vote by Arbitrum DAO governance. That approach reflects a trade-off in some blockchain systems: emergency intervention can limit an attacker's options, but it depends on specific decision-makers and governance steps.
Aave took a different precaution. After the exploiter deposited 60 million USDT and borrowed 19,762 WETH (about $44.6 million at the time), the protocol froze markets across its V3 and V4 deployments. Risk service provider LlamaRisk said the position had about $59.9 million in USDT collateral against $43.8 million in debt at the reported snapshot. The position remained subject to normal liquidation and was not reported as putting Aave suppliers at risk.
The freeze limited new deposits and borrowing across many markets, but it didn't stop users from withdrawing funds or repaying loans. That distinction matters: pausing new exposure can reduce risk while still leaving some exit and repayment options. If the pause lasts too long, liquidity and borrowing rates can still be affected - especially if withdrawals drain available capital.
Market makers and broader market conditions
Trading firms Wintermute and GSR said they had exposure to Binance but didn't expect major operational disruption. GSR said its exposure was below 5% of net equity; Wintermute said it was below 20%. Neither company disclosed a dollar figure or confirmed losses. Market makers help maintain order flow, so reduced access to exchanges can make trading harder and potentially more expensive.
Crypto prices also moved during the reporting period. Bitcoin traded near $76,937, down 4.9% over 24 hours, while BNB fell about 8% and Ether about 5.7%. AAVE and UNI also declined. These price moves coincided with the incident, but short-term changes alone can't prove the hack caused each move. Prices reflect multiple factors, including liquidity, risk sentiment, and concurrent news.
What does the incident mean for users and crypto markets?
For Binance customers, the main issue was service availability and verified information. A temporary pause in deposits or withdrawals can be a safety measure, not proof that customer balances are missing. Still, users need clear updates on what's affected, when services will restart, and how balances are being reconciled.
Binance said it would cover all losses and that the incident didn't affect Binance.US. Those are useful statements, but they don't replace the final post-mortem or a full account of what happened. Until then, users should stick to official notices and verified company updates for operational instructions, and avoid links or direct messages claiming to offer "emergency withdrawals," refunds, or recovery services.
What users should do during an exchange incident
A good instinct is to avoid making things worse while you wait for verified information. If you use Binance or another affected service:
- Check the status of the exact service you use. Deposits, withdrawals, trading, and other products may be paused independently.
- Don't share credentials or recovery phrases. Support teams don't need your seed phrase to verify anything.
- Treat unsolicited recovery offers as suspicious. Scammers often target major incidents to impersonate exchanges or investigators.
- Keep records of balances and transactions. Account statements, transaction IDs, and timestamps can help later during reconciliation or support.
- Avoid rushed transfers based on unverified claims. Moving funds to an unfamiliar address can create another, separate, irreversible loss.
These steps aren't a replacement for the exchange's incident response. They're basic operational hygiene while services and facts are still evolving.
The larger custody and resilience question
This incident also underlines something practical for institutions and individual traders: assets held on an exchange depend on that exchange's custody, signing, and operational controls. Self-custody can reduce reliance on a centralized custodian, but it shifts the responsibility for key management, backups, and transaction approvals to the user. Either way, risk doesn't disappear - it just changes where it sits.
For exchanges, the post-mortem should explain the attack path, the systems affected, how transaction approvals were validated, and what controls changed afterward. For protocols and issuers, the test is whether freeze procedures are clear, narrowly scoped, and accountable. For users, the real question isn't just "centralized vs decentralized." It's whether the platform's failure modes are understood and whether the response can be checked.
Key takeaways
- Chainalysis estimated about $5.912 billion was stolen, while Binance reported $3 billion in verified frozen assets by October 30. These are different measures, not interchangeable totals.
- Binance temporarily suspended deposits and withdrawals during security checks and said it would cover all losses. The full customer impact hadn't been established in the October 30 updates.
- Blockaid's suggestion that transaction-signing infrastructure may have been misused is still preliminary. The exact method remained under investigation.
- Stablecoin issuers and Arbitrum froze or restricted some assets. Aave paused new activity across markets while still allowing withdrawals and loan repayments.
- Rely on official service notices for account actions. Don't trust unsolicited recovery messages or move assets based on unverified claims.
Conclusion
This Binance incident is a reminder that a major crypto breach isn't captured by a single headline number. Estimated stolen value, visible wallet balances, frozen assets, and recovered funds are different measures, and the numbers can shift as investigators verify addresses and trace transfers.
As of October 30, Binance reported $3 billion frozen, while Chainalysis estimated $5.912 billion stolen. The technical cause and final user impact were still unresolved. For now, the best approach is to follow verified service updates, protect account credentials, and wait for a detailed post-mortem before drawing conclusions about how the breach happened or what was ultimately lost.