Binance Hack: Fake Job Interview and AI Tool Behind $6.3B Theft

How the attack unfolded, June to October 2026

"This wasn't one mistake or one breach," Teng wrote on X. The report bears that out. The sequence, as Binance described it:

1. June: a Wallet DevOps engineer installed a tampered Homebrew package while looking for an AI coding tool. Binance detected the anomaly, replaced the device and rotated credentials. The attackers still learned who worked on the wallet team and in which roles.
2. September: a second software engineer, contacted through a job platform, went through a fake hiring process with video calls with a supposed HR manager and the chief executive of a fictitious company. He downloaded a coding assignment that infected his work computer.
3. 20 October: using that computer and an internal AI tool, the attackers took control of the devices of two wallet engineers. On one, they found a permission to deploy containers in production.
4. 29 October, 20:05 UTC: the attackers deployed a container running a malicious script inside the wallet-signing environment. Funds began leaving Binance.
5. 30 October, 00:10 UTC: Binance completed containment, just over four hours after the first outflows.
6. 31 October: the SAFU emergency fund's bitcoin balance fell from 15,000 BTC to 7,500 BTC as Binance drew on it.
7. 3 November, 04:00 UTC: withdrawals reopened in phases for dozens of further assets across multiple networks.

Three engineers' machines were compromised in the chain that mattered. None of the steps required breaking cryptography.

Why an internal AI tool and MPC slowed containment

The report's least familiar detail is the role of the AI tool. Binance has not named it or described its permissions in public. What the account shows is that a tool built to help staff move across internal systems did the same for the attackers.

The signing layer added a second problem. According to CryptoTicker's reading of the report, the attackers used an EIP-7702 delegation to gain execution rights over a hot wallet. Binance's wallets use multi-party computation, in which multiple parties produce each signature and no single key holds the full secret. Binance security chief Jimmy Su said no single key was able to revoke the permission once granted, which pushed containment past midnight. A design meant to remove single points of failure also removed the single point of shutdown.

Binance said it has closed the entry points, rebuilt the affected wallet system in a new environment, replaced devices, decommissioned the engineers' credentials and tokens, and commissioned an independent security review. It also plans more spending on AI-based anomaly detection and a security research fund. "This should not have happened," the company wrote, and apologized to users.

Outflows, recovery and the numbers so far

The withdrawal figures grew as more networks reopened. Reuters reported $4.72 billion in net outflows on 2 November. CoinDesk's figures from Teng a day later put the totals higher:

• Withdrawals: $10.97 billion in the 46 hours after the hack.
• Net outflow: $5.28 billion, after $5.69 billion in deposits between 1 November and early 3 November.
• Peak hour: $1.24 billion withdrawn and $936 million in net outflow, on 1 November.
• Turning point: by 03:00 UTC on 3 November, hourly deposits exceeded withdrawals by $10 million.

On the loss itself, Binance says it has frozen or intercepted $2.85 billion of the stolen assets and replenished 98% of impacted holdings with company funds. The stolen total appears as $6.3 billion in Reuters and the report summary, $6.34 billion in The Block and $6.4 billion in the CoinDesk article body. SAFU, now holding 7,500 BTC, is to be refilled to $1 billion with no date set.

Attribution, and what the case means for Canadian readers

The FBI has attributed the attack to TraderTraitor, a group it links to North Korea. North Korea rejects the claim, and Kim Jong-un's sister called it a "grave political provocation." The attribution is an assessment by US authorities. No one has been charged, and no court has ruled on it. Binance says it detected and stopped 57 suspected North Korea-linked attacks using similar methods in 2026.

Canadian residents had no direct exposure, since Binance left Canada in 2023. The method travels, though. Fake recruiters targeting developers with coding tests are not specific to Binance, and anyone working at a Canadian crypto firm, fintech or exchange is a plausible target. The defense starts with a rule that sounds dull. Run interview code on a machine that holds no work access, and verify a recruiter's company before the second call.

The case also adds weight to the custody model Canadian registered platforms follow under CSA terms, with at least 80% of client crypto held by third-party custodians. The Binance loss came from hot wallets. Every control in this report sat between an engineer's laptop and those wallets, and each one gave way in turn.