🔍 Read the full analysis: Fake AI Recruiters: Lessons From Binance’s $6.3 Billion Hack on ThorstenMeyerAI.com
Get business pricing on tech for your team
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
Binance’s November 3 report says attackers used a fake recruitment process and malicious coding assignment to compromise an engineer’s work computer, then used an internal AI tool and a deployment token to reach its wallet signing service. The exchange put the assets affected at about $6.34 billion and said about $2.85 billion was frozen or intercepted. The report does not explain how the internal AI tool was used or identify the tool installed in an earlier incident.
Binance said on November 3 that a fake recruitment process helped attackers compromise an employee’s work computer and reach the cryptocurrency exchange’s wallet signing system, where they moved about $6.34 billion in digital assets on October 29. The company’s account describes a months-long campaign involving malicious code disguised as a coding assignment, an internal AI tool and a container deployment permission token; it says about $2.85 billion was frozen or intercepted.
According to Binance, a software engineer was approached in September on a legitimate job-hunting platform by someone posing as a project director. The engineer’s profile identified his Binance employment. The company says he took part in two rounds of interviews: first a live video call with a person posing as a human resources representative, then a conversation on a chat app with someone claiming to be the CEO of a nonexistent company. The second contact sent a coding assignment that the employee downloaded onto his work computer.
Binance says the assignment contained a new, undetected malware sample that ran during setup. The report says the malware replaced a legitimate developer tool with a malicious copy and removed traces of its activity. The company said endpoint security tools did not detect the malware at the time. It did not publish the malware’s name or give technical indicators in the account provided.
The exchange’s timeline also reaches back to June. Binance says a Wallet DevOps engineer had installed a popular AI coding tool using a tampered Homebrew installation. The company says it detected that incident, replaced the device and rotated credentials, but does not name the AI tool or establish that the earlier infection was the same operation as the later recruitment attack. On October 20, Binance says, the attacker used an internal AI tool to gain control of the DevOps engineer’s machine and another engineer’s computer.
On the DevOps machine, the attacker found a container deployment permission token, Binance says. On October 29, the attacker used stolen credentials to deploy a container and run a malicious script. From 20:05 UTC, funds moved through Binance’s internal wallet signing service outside the normal withdrawal process. Binance said the attack affected about $6.34 billion in assets, around $2.85 billion was frozen or intercepted, and 98% of affected tokens had been replenished from the company’s own funds by October 31.
Infographic 01 · From job offer to wallet
Five steps from a fake interview to $6.34 billion
How Binance describes the campaign in its initial findings of 3 November. Engineers are named only as A, B and C.
- June · the lureEngineer A (wallet DevOps) installs “a popular AI coding tool” through a tampered Homebrew installation. Caught, device replaced, but his team is now known.
- September · the interviewEngineer B is approached on a legitimate job platform. Video call with fake HR, chat with a fake CEO, then an “assignment” to download.
- Setup · the infectionThe repository’s code runs on his work computer. 0-day malware, missed by endpoint security, swaps a developer tool for a malicious copy.
- 20 October · the jumpAn internal AI tool is used as a springboard to take over Engineers A and C. A container deployment token sits on A’s computer.
- 29 October · the theft17:15–19:56: container deployed, script triggered. From 20:05 UTC funds leave via the wallet signing service.
- Three engineers’ machines were in the path, not one laptop.
- No single private key existed to revoke the Ethereum delegation: the hot wallet used MPC.
- The delegation was cleared at 00:10 UTC on 30 October.
- The job platform and the chat app.
- The AI coding tool and the internal AI tool.
- How the internal AI tool was abused.
Source: Binance, initial findings, 3 Nov 2026. Binance gives no time zone for 17:15–19:56; its other times are UTC. Simplified; no commands or file paths reproduced.
Powered by Thorsten Meyer AI
Hiring Became an Entry Point
The account shows how a hiring process can expose a company’s systems when an employee is persuaded to run code on a work device. The reported route did not depend on a simple suspicious email: it combined a professional profile, staged interviews and a software assignment that appeared to be part of recruitment. That makes the incident relevant to employers as well as job seekers, particularly teams whose staff have access to production infrastructure.
Binance’s description also connects endpoint access to a consequential internal permission. A token on an engineer’s computer, rather than a reported leak of wallet private keys, gave the attacker a route to deploy software and invoke the exchange’s signing service. Binance’s earlier October 30 statement said it had found no evidence of wallet private key leakage; the November 3 report adds detail about how the attacker reached the signing process. That distinction matters: the reported compromise was of systems and authorization paths, not a confirmed theft of private keys.
The financial response is also significant. Binance says most of the affected tokens were replenished from its own funds by October 31, while a portion was frozen or intercepted. Those are figures reported by the exchange, not an independently verified accounting in the material available here. The report does not specify the final amount of unrecovered assets or give a full breakdown by token and network.
Products Worth Considering
Bose SoundLink Flex Bluetooth Speaker (2nd Gen) – Portable Outdoor Speaker with Hi‑Fi Audio, Waterproof and Dustproof, USB‑C, Up to 12 Hours
LG UltraGear 34GX90SA-W 34-inch WQHD Curved OLED Gaming Monitor
Apple MacBook Air 13-inch with M5 chip, 16GB memory, 512GB SSD, and 12MP Center Stage camera
As an affiliate, we earn on qualifying purchases.
From June Installation to October Theft
Binance’s report changes the apparent timeline from a short wallet incident to a campaign that it says began months earlier. Its October 30 account had identified a compromised DevOps engineer’s laptop and said there was no evidence that wallet private keys had leaked. The November 3 report describes the recruitment approach and the attacker’s subsequent movement between employee machines, while retaining the distinction between access to the signing system and access to private keys.
The company labels the employees Engineer A, B and C rather than naming them. Its account places the altered Homebrew installation in June, the fake recruitment approach in September, the use of an internal AI tool on October 20, and the deployment and asset movements on October 29. Binance describes the operation as a “sophisticated, multi-stage campaign,” rather than a single isolated breach or simple phishing attempt.
Attribution remains a claim by authorities. Binance cites the FBI, which attributes the activity to North Korea and calls it “TraderTraitor.” North Korea denies involvement, according to the source material. The provided account does not include independent forensic findings supporting that attribution, so it should be treated as an official allegation, not an established conclusion.
How the Internal Tool Was Used
Binance has not explained how the attacker used its internal AI tool, what access the tool had, or whether the tool itself was compromised. The report also does not name either the internal tool or the popular AI coding tool involved in the June installation. It does not establish whether the June event and September recruitment operation were conducted by the same individuals, although Binance presents them within its account of the broader campaign.
Other details remain incomplete. Binance does not identify the job platform or chat app, publish the malicious repository, or say precisely how the attacker obtained the credentials used in the October 29 operation. Its report gives a 17:15–19:56 window for activity on employee computers without specifying a time zone for that interval; it separately says funds began moving from 20:05 UTC. The available source material also does not provide independent verification of the loss, recovery or attribution figures.
Security Review and Recovery
The next steps are for Binance to provide further detail on the incident’s technical scope, the role and permissions of the internal AI tool, and the final disposition of affected assets. The company’s figures currently describe the amount impacted, the amount frozen or intercepted, and the share of tokens replenished by October 31; a final accounting is not included in the report summarized here.
For organizations, the account points to practical review areas: whether employees may run outside code on company devices, how deployment tokens are stored and scoped, and what access internal developer tools can exercise. Job seekers should also treat requests to run a recruiter’s coding assignment on an employer-owned computer as a security risk. These are lessons drawn from Binance’s account, not proof that every hiring test or AI coding tool presents the same risk.
Binance’s report is an initial detailed account, and further findings may clarify the attack path and recovery. The FBI attribution remains an official claim cited by the exchange, while North Korea’s denial and the lack of detailed independent forensic evidence leave responsibility disputed in the material available so far.
Key Questions
What happened in the Binance hack?
Binance says attackers used a fake recruitment process to get an engineer to download a malicious coding assignment onto a work computer. They later used access to employee machines and a container deployment token to reach Binance’s wallet signing service and move digital assets.
How much was affected, and how much was recovered?
Binance reported about $6.34 billion in assets affected and about $2.85 billion frozen or intercepted. It said 98% of affected tokens had been replenished from its own funds by October 31. The source account does not provide a final independent accounting of unrecovered assets.
Did attackers steal Binance wallet private keys?
Binance said on October 30 that it had found no evidence of wallet private key leakage. Its later report describes attackers reaching the internal wallet signing service through compromised systems and credentials; it does not say that private keys were stolen.
What role did AI tools play?
Binance says a popular AI coding tool was installed through a tampered Homebrew installation in June, and that an attacker used an internal AI tool on October 20 to gain control of two engineers’ machines. The company has not named either tool or explained how the internal tool was used.
Who does the FBI blame for the attack?
Binance cites the FBI as attributing the activity to North Korea under the label “TraderTraitor.” North Korea denies involvement, and the source material does not include independent forensic evidence that resolves the attribution.
Source: ThorstenMeyerAI.com
