🔍 Read the full analysis: Could An AI Job Offer Be A Setup? Lessons From Binance on ThorstenMeyerAI.com
Get business pricing on office and shipping supplies
- Business-only prices and quantity discounts
- Tax-exempt purchasing
- Multiple users, one account, clear invoices
TL;DR
In a report published November 3, Binance said attackers used a fake job interview and malicious coding assignment to compromise an engineer’s work computer, then moved through employee devices and used a deployment token to reach its wallet signing service. Binance put affected assets at about $6.34 billion and said about $2.85 billion was frozen or intercepted; it did not explain how its internal AI tool was used or provide a full account of the attack.
Binance said on November 3 that attackers used a fake job interview and a malicious coding assignment to compromise an employee’s work computer before an October 29 incident affecting about $6.34 billion in digital assets. The exchange’s account describes a campaign that began in September, spread across employee devices and ultimately used a deployment permission token to reach its wallet signing service.
According to Binance, an attacker contacted a software engineer in September through a legitimate job-hunting platform, posing as a project director. The engineer took part in two rounds of interviews, including a video call with someone claiming to work in human resources and a later chat with a person presenting as the CEO of a company Binance said did not exist. The engineer was asked to download a coding assignment onto a work computer. Binance said the repository contained malicious code.
Binance described the malware as a previously undetected, zero-day tool that was not identified by endpoint security software at the time. The report says it replaced a legitimate developer tool with a malicious copy and removed traces of its activity. Binance has not publicly identified the employees involved, referring to them as Engineers A, B and C.
The exchange says the attacker later used an internal AI tool to gain control of Engineer A, a wallet DevOps engineer, and Engineer C, a wallet software engineer. On Engineer A’s computer, the attacker found a container deployment permission token. Binance says the attacker used credentials associated with that engineer to deploy a container and run a malicious script, then reached the wallet signing service. The service was used outside the normal withdrawal process. Binance’s report does not describe precisely how the internal AI tool enabled access.
Binance estimated that about $2.85 billion was frozen or intercepted and said 98% of the affected tokens had been replenished from company funds by October 31. Those figures are Binance’s account; the report excerpt does not provide a breakdown of the calculations or independently verified totals.
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 Scams Reached Production Systems
The account shows how a recruitment interaction can become an entry point into a company’s internal systems. A coding exercise that appears routine may expose an employee’s work device to malicious software, and that access can matter well beyond the person who received the invitation. In Binance’s account, the attack moved from one engineer to other employees and eventually reached credentials and permissions connected to wallet operations.
For employers, the reported route puts candidate screening, endpoint security and access controls in the same risk picture. Companies can limit exposure by keeping coding tests in isolated environments, restricting deployment permissions, rotating credentials after suspected compromise and avoiding long-lived sensitive tokens on employee laptops. These are general security implications, not measures Binance said it had adopted in response to this incident.
For job seekers, the practical warning is narrower: a request to run unfamiliar code on a current employer’s computer carries risk, even when interviews appear professional. The episode also cautions against treating the presence of AI tools as proof that AI caused an intrusion. Binance says an internal AI tool was part of the attackers’ path, but has not explained its function.
Popular right now
Dyson Big Ball Multi Floor Canister Vacuum, Yellow
Dyson W1 PencilWash Wet and Dry Cleaner with Dok Cordless Wet Floor Cleaner
Apple AirPods Pro 3 Wireless Earbuds with Active Noise Cancellation
As an affiliate, we earn on qualifying purchases.
From June Install to October Attack
Binance’s timeline begins in June 2026, before the fake interview. The company says Engineer A downloaded a tampered Homebrew installation while trying to install an unnamed popular AI coding tool. Binance’s security team detected that incident, replaced the device and rotated credentials, according to the report. The exchange says the attacker nevertheless learned about the engineer’s role and colleagues on the wallet team. Binance linked to a security write-up about a fake Homebrew site promoted through a search advertisement, but did not say that the same campaign compromised Engineer A.
Binance places the job-platform approach in September and the move between employee machines on October 20. On October 29, the attacker deployed a container and ran a script before assets began leaving through the signing service. The report says most of the funds moved during a short period that evening, but its detailed account also makes clear that the activity had started weeks earlier.
In an earlier statement on October 30, Binance had identified a compromised DevOps engineer’s laptop as a possible factor and said it had found no evidence that wallet private keys were leaked. The November 3 report adds a proposed route into the company and a description of how the signing system was reached. Binance characterizes the incident as a multi-stage campaign, rather than a single phishing event.
Key Steps Still Undisclosed
Binance has not explained how the internal AI tool was used, what access it had, or how it enabled control of the other employees’ devices. The company also has not named the employees, the job platform, the chat application, the fake company or the AI coding tool involved in the June installation.
The report does not give a time zone for every stage of the attack or a complete technical account of the container deployment and signing-service interaction. Binance said no evidence showed that wallet private keys were leaked, but that statement does not by itself establish every detail of how the attacker accessed or directed the signing system. The source material reports the FBI’s attribution to North Korea and says North Korea denies it; it does not provide the underlying evidence needed to independently assess that attribution.
The financial figures are also Binance’s estimates. The source gives totals for assets affected, frozen or intercepted, and replenished, but does not detail the asset-by-asset accounting, the final amount unrecovered, or how the 98% replenishment figure was calculated.
Further Technical Details Needed
Binance’s November 3 report provides a fuller account than its October 30 statement, but the information available here does not specify whether the exchange plans to publish additional technical findings or a final accounting. Further disclosures would help clarify the AI tool’s role, the extent of the affected systems and the status of the assets that were not frozen or intercepted.
Readers should distinguish any later company statements from independent confirmation. Relevant next updates would include a more detailed incident timeline, an explanation of the signing-service controls involved, and any additional findings from investigators. Until those details are available, Binance’s report remains the principal source for how the exchange says the attack unfolded.
Key Questions
How did the attackers reportedly gain access to Binance?
Binance says an attacker posed as a recruiter, conducted two rounds of interviews and sent an engineer a malicious coding assignment to run on a work computer. The company says attackers later moved between employee devices.
What role did an AI tool play?
Binance says the attacker used an internal AI tool on October 20 to gain control of two employees’ machines. The report does not explain how the tool worked or what it enabled.
How much was affected, according to Binance?
Binance put affected digital assets at about $6.34 billion and said about $2.85 billion was frozen or intercepted. It also said 98% of affected tokens had been replenished from company funds by October 31. These are figures reported by Binance.
Were wallet private keys stolen?
Binance said on October 30 that it had found no evidence of a wallet private-key leak. Its later account says the attacker reached the wallet signing service, but the source material does not establish that private keys were stolen.
Who does the FBI say was responsible?
Binance cited the FBI as attributing the activity to North Korea and using the label “TraderTraitor.” The source says North Korea denies involvement; the attribution is not independently established by the material provided.
Source: ThorstenMeyerAI.com
