Binance breach: what we know—and how to reduce your risk.
Published October 30 · Updated November 7, 2026
Archive follow-up · November 7, 2026. First published October 30. Service availability varies by asset and network.
What changed since October 31?
How the transfers happened. In its November 3 initial investigation, Binance says attackers gained access to its internal wallet signing service. On Ethereum they used that access to authorize a contract to move funds. Pausing exchange withdrawals did not cancel the permission already recorded on the blockchain; Binance had to revoke it separately. This explains how funds could move without an attacker extracting a wallet private key. The findings are preliminary, and Binance says it is seeking independent review.
Attribution and losses. The FBI attributed the theft to North Korea on October 31. Binance estimated on November 3 that $6.34 billion was affected and roughly $2.85 billion had been frozen or intercepted. Freezing funds limits their movement; it does not establish that they have been returned.
Replacing the assets. In its November 4 recovery update, Binance said it had replenished about 98% of the affected amount using its own resources. It was still buying the less liquid tokens. That percentage measures replacement, not recovery from the attackers.
Checking reserves and withdrawals. The November 4 reserve snapshot covered 44 tokens, up from ten. On November 6, Binance announced that its verification proof was ready. The proof lets holders check covered balances at the snapshot time; it is not a full audit of exchange liabilities. Separately, its November 6 withdrawal notice listed another group of asset and network pairs for phased reopening. Check your exact pair in the official app before initiating a transfer.
OUR VIEW · ANALYSIS
Reported evidence points to an exchange custody and authorization failure, not proof that Bitcoin’s cryptography or blockchain consensus was broken. Strong personal security matters, but it cannot eliminate a custodian’s operational risk. Long-term adoption requires resilient custody as well as useful applications.
October 30–31 reporting: preliminary findings and earlier recovery targets
PRIVATE KEYS · PRELIMINARY FINDING
Binance says it has found no evidence of leaked wallet private keys. The investigation is ongoing. This does not rule out misuse of signing permissions or internal systems. An attacker can cause unauthorized transactions without extracting a private key; the final technical report is still pending.
Binance reports 90% of affected assets replenished, up from approximately 80%. It says BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD and ZEC are fully backed. The remaining tokens are less liquid and still being acquired.
Replenishment uses corporate resources; it does not mean stolen assets have been recovered. These are company claims, not our independent audit.
SERVICE STATUS · COMPANY TARGET
Withdrawals targeted for November 1
Binance targets Sunday, November 1 for reopening withdrawals. This is not confirmation that withdrawals have resumed. Check official service announcements before acting.
RESERVES · VERIFICATION PENDING
Snapshot published; full proof pending
Binance says its October 31, 00:00 UTC reserve snapshot is published, with the full zero-knowledge proof estimated for November 3 UTC.
A reserve snapshot is not a complete independent assessment of liabilities or solvency.
In its October 30 Update #2, Binance estimated losses of approximately $6.3 billion and about $3 billion frozen. Frozen does not mean returned. It also reported additional breach points beyond the preliminary compromised-laptop theory; the complete attack path remains under investigation. It continued to report no evidence of leaked wallet private keys.
Published October 30: TRM Labs reported approximately $6.36 billion moved across ten blockchains and attributed the attack to North Korea’s TraderTraitor group with high confidence. Its initial figures reflect observations through October 30 at 00:30 UTC. Attribution is an investigator assessment, not a final forensic conclusion.
Updated October 31: replaced the earlier relative withdrawal-restoration estimate with the company’s dated target; added the latest replenishment and reserve-verification milestones; clarified that the initial laptop explanation is incomplete. The original publication date and permanent article URL are preserved.
These measures reduce specific risks. None guarantees safety or would necessarily stop an exchange’s internal systems from being compromised.
01 · ACCOUNT ACCESS
Protect the account and its email
Use unique passwords and phishing-resistant passkeys or hardware security keys where supported. Secure the associated email account too. Keep recovery methods current and backup codes somewhere safe; losing every authentication method can lock you out.
Prefer stronger MFA to relying solely on SMS. Never approve an unexpected login prompt or share a one-time code.
02 · PERMISSIONS
Limit what can move funds
Enable withdrawal-address allowlists and change delays where available. Review sessions, connected applications and API keys; revoke unused access. For a tracker, use read-only permissions without trading or withdrawal access. Apply IP restrictions where supported.
These controls protect your account; they are not insurance against an exchange-wide failure.
03 · PHISHING
Ignore recovery and “safe wallet” messages
Open the official app or a verified bookmark yourself. Do not follow unsolicited refund links, pay a recovery fee, or transfer crypto to a supposed support agent’s safe wallet. Never give anyone your seed phrase or private keys.
Scammers can impersonate support during a real incident. Verify requests independently through official support.
04 · CUSTODY CHOICES
Match custody to your needs and skills
Consider limiting exchange balances to what you need for trading or other services. Self-custody can reduce exchange exposure, but puts key protection, backups and transaction mistakes on you. A hardware wallet is not protection against every malicious approval.
Learn the recovery process before moving material holdings. Store seed backups offline and securely; do not photograph them or upload them to cloud storage.
05 · TRANSFERS & SIGNATURES
Verify before you approve
Check the destination address on the hardware wallet’s own screen, the network, amount and any required memo or tag. Begin with a small test transfer and confirm receipt. Read transaction and token-permission requests; reject those you do not understand.
A successful test does not make future approvals safe. Separate long-term storage from wallets used to try unfamiliar applications.
06 · IF YOUR ACCOUNT LOOKS COMPROMISED
Use official support and preserve records
From a trusted device, secure your email and exchange login, revoke suspicious sessions and keys, and contact official support. Preserve transaction IDs, account statements and messages. Do not attempt to bypass withdrawal restrictions through strangers or unofficial services.
If you suspect your seed phrase was exposed, changing an app password does not secure the underlying wallet.
Security sources and scope
Security guidance checked October 30, 2026. Feature names and availability differ by platform and jurisdiction. Reporting here concerns Binance.com; it does not establish the same incident or service status at Binance.US.
Restoration of the remaining withdrawal routes; independently assessed reserves and liabilities; recovered funds versus merely frozen funds; completed customer coverage; and a technical post-mortem explaining how unauthorized transactions passed approval controls. Proof of reserves alone does not establish all liabilities or overall solvency.
TAKEAWAY · OUR VIEW
Separate asset risk, protocol risk, custody risk and your own account security. A sound blockchain can still be accessed through a vulnerable intermediary. Choose where you hold assets as deliberately as you choose what to hold.