Plan this weekPlatform changes

Binance says a hack cost about $6.3 billion: what is confirmed and what to do if you keep money on an exchange

Binance said on 29 Oct 2026 that a compromised laptop led to unauthorized withdrawals worth about 6.3 billion dollars. It froze about 3 billion and says user funds are safe. Here is what is confirmed, what is not, and what to check.

Updated 5 Nov 2026: see what changed

How urgent

Plan this week

Who is affected

People who hold funds on Binance (deposits and withdrawals are suspended while Binance investigates), and any team whose staff use work laptops with access to production systems

What to do

Do not move funds in a hurry. Follow Binance's official announcements for when withdrawals reopen, turn on app-based two-factor sign-in and a withdrawal allow list, and ignore any message that offers compensation or asks you to verify your account

Published 30 Oct 2026 · Sources last checked 5 Nov 2026No. 30 / 87

Updates, follow-ups and corrections

  1. Update · 5 Nov 2026. Binance published its initial findings on 3 Nov 2026 and we read the report itself. It says about 6.34 billion dollars were affected, about 2.85 billion were frozen or intercepted (a figure still being reconciled) and 98 percent of the affected tokens had been replaced by 31 Oct. According to the report, the way in was a fake job interview: in September an engineer was told to download an "assignment" that ran malicious code, and by 20 Oct the attacker used that computer and an internal AI tool to reach two more engineers, one of whom held a deployment token that led to the wallet signing service on 29 Oct. Binance does not attribute the attack itself: it cites an FBI release. This replaces what we said below about the way in, the amount frozen and the full report, which is now published. It is still a preliminary report.
  2. Update · 2 Nov 2026. SecurityWeek reports that on 31 Oct the FBI formally blamed North Korea for the theft, naming the group TraderTraitor, the one it also blamed for the Bybit theft. According to that report, the FBI listed 608 Ethereum addresses, 19 Bitcoin addresses and one Solana address that hold or held proceeds, and asked crypto services and analytics firms to refuse transactions linked to them. This replaces what we said below about attribution: earlier, only analytics firms pointed to North Korea and Nextgov reported the FBI had not attributed it. We read this through SecurityWeek, not the FBI notice itself, and Binance has not published its post-mortem yet.

We keep the original text. When something changes, when we follow a story, or when we get something wrong, we add a dated note here instead of editing silently.

What happened

On Thursday 29 October 2026, users reported funds draining from Binance's wallets. Binance confirmed a security incident and suspended deposits and withdrawals. Later that evening it posted on X that the estimated total impact is around 6.3 billion dollars, and warned that this figure, and the amount frozen, could change. If confirmed, it would be the largest crypto theft on record.

According to NBC News, which quotes Binance's post, the attack began with a compromised laptop. That gave the attacker access to a service container, from which they submitted unauthorized withdrawal transactions. CoinDesk describes it as an engineer's laptop; NBC does not say whose laptop it was.

Binance says it has identified and frozen about 3 billion dollars that passed through wallets linked to the attackers, that it will cover all losses, and that user funds are safe. Tether's chief executive said on X that Tether froze more than 1.567 billion dollars, and Circle's said it froze more than 800 million, in coordination with law enforcement. Changpeng Zhao, Binance's founder and now a shareholder, wrote on X that it "does look like a hack".

What Binance's report says (3 November)

Binance's own report, which we read directly, describes a multi-stage campaign, not a single breach:

  • June: an engineer on the wallet team installed an AI coding tool from a tampered package found through a search engine. Security noticed and replaced his computer, but his role and his colleagues' roles stayed exposed.
  • September: someone posing as a project director contacted another engineer on a job platform. After two interviews, the second with a fake "CEO", he was told to download an assignment to his work computer. The code ran at install, swapped a trusted developer tool for a malicious copy and was not detected by Binance's endpoint tools.
  • 20 October: the attacker used that computer and an internal AI tool to take control of two more engineers. One held a container deployment token.
  • 29 October: using that token, the attacker reached the wallet signing service and moved assets outside the normal withdrawal process. Binance says the attacker abused an Ethereum authorization feature (EIP-7702) so transfers could continue after withdrawals were paused, and that the last unauthorized transfer was finalized at 23:56 UTC and the permission revoked at 00:10 UTC on 30 October.
  • Numbers (Binance): about 6.34 billion dollars affected, about 2.85 billion frozen or intercepted by 3 November, 98 percent of the affected tokens replaced by 31 October.
  • Who: Binance does not attribute the attack itself. It cites an FBI release that points to North Korea. Binance says it has not tied the employee compromise to a specific campaign.

Our full walkthrough is in the Expediente video on this case. The report is preliminary and Binance says independent reviews are still to come.

Who is affected

Binance says customer funds are safe, but while deposits and withdrawals are suspended you cannot move your money. NBC News notes that funds held on an exchange are not automatically insured, so being reimbursed depends on the exchange keeping its promise. For everyone else, the lesson is about work laptops: in this case, a single compromised device was the reported way in.

What to do

Our advice, not Binance's:

  1. Do not move funds in a hurry. Follow Binance's official announcements, typing the address yourself, for when withdrawals reopen.
  2. Turn on app-based two-factor sign-in (an authenticator app or a passkeyPasskey A way to log in with your fingerprint, face or device PIN instead of a password, tied to the real site so it cannot be handed to a fake one. Tap again to open the glossary, not SMS) and a withdrawal allow list, if your exchange offers it.
  3. Ignore any message that offers compensation or asks you to log in "to verify your account". Scammers use big incidents like this one.
  4. Only use the official app or the site address you typed yourself, never a link from a message.

If you build with AI tools

Our advice, not from the reports: treat the laptops of anyone who can reach production as part of your attack surface. Keep admin access on separate, locked-down machines, use short-lived credentials, and put limits and a second approval on anything that moves money or keys.

What we could not confirm

We did not read Binance's posts on X directly: the quotes come from NBC News and CoinDesk. The final amount is not settled; analysts estimate between 5.3 and 5.8 billion, and some caution that their tallies may include unrelated transfers. Who is behind it is not confirmed: Binance says it is working with law enforcement, and some press and analytics firms point to North Korean groups, but Binance has not said so. Blockaid proposes that an EIP-7702 delegation transaction was involved, and Bitcoin.com notes that this does not explain the Bitcoin and Tron movements, so we treat it as a hypothesis. Binance published its initial findings on 3 November (see above); they are preliminary, and we do not know which exact North Korean campaign this was, how the internal AI tool was compromised or what the independent review will find. We will update this page when that changes.

Watch the short video

The video loads from YouTube (privacy-enhanced mode) only when you press play.

Comments

No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.

    We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.

    Sources and verification

    We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.

    Spotted a mistake? Email [email protected] and we will correct it and note the change.

    Get the free runbooks

    One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

    Send me the runbooks