SafetyRisk, alignment & guardrails
Binance says fake job interviews and an internal AI tool led to $6.3 billion crypto theft
Binance's incident report traces a record crypto theft to months of intrusion aimed at developers: a tampered Homebrew install, a malware-laden fake job interview and an internal AI tool used to obtain wallet credentials and a deployment token before hot wallets were drained.
From the CNBC · Technology article of November 3, 2026 and cited sources: The attack chain ran through developer tooling. [1] [3] [7] [8]
SOURCES[1] Binance co-CEO Richard Teng says hackers used fake job… cnbc.com[3] Binance incident report binance.com[7] The Block: incident report details theblock.co
AT Pulse research deskPublished · Updated · 5 min read · AI-assisted analysisAI-assisted, not human-edited. Methodology Corrections Who owns this site
- Original source
- CNBC · Technology article, independent perspective
- Brief by
- AT Pulse research desk AI-assisted; publisher and contact on the desk page
- When
- November 3, 2026 article published
- Covered
- Nov 4 edition
- Evidence
- 12 sources across 11 sites
- 1Binance co-CEO Richard Teng says hackers used fake job…cnbc.com
- 2Hackers behind $6.3bn Binance heist ‘used malware and…theguardian.com
- 3Binance incident reportbinance.com
- 4BleepingComputer: FBI links heist to North Koreableepingcomputer.com
- 5Elliptic: largest hack in historyelliptic.co
- 6CoinDesk: North Korea denies rolecoindesk.com
RisingHow it’s measured
Hacker News · 24 likes · 4 comments
Reach blends public engagement (views, likes, comments, shares, stars) from the platforms where the story or its original source lives: YouTube, Hacker News, GitHub, Substack and similar. A video and the article written from its transcript share one score, taken from the video. Platforms with no data are left out rather than counted as zero, and the age of a story never lowers its score.
The attack chain ran through developer tooling. In June a wallet engineer installed a tampered Homebrew while setting up an AI coding tool. In September fake recruiters delivered a coding test hiding obfuscated malware. On October 20 attackers used an internal AI tool to obtain wallet-team credentials and a container deployment token. On October 29 they used a malicious container against the wallet-signing service. [1] [3] [7] [8] [9]
No private keys were extracted. Instead, a signer approved transactions it should have rejected. An EIP-7702 delegation also gave a malicious contract partial control of a hot wallet, so theft continued after withdrawals were suspended. Security firms disagree on how much that delegation added to the losses. [3] [9] [10]
Binance's report says attackers reached a signing service through developer tooling and an internal AI tool rather than by stealing keys.
Read the full assessment
The implication: internal AI assistants with credential access can become lateral-movement paths and need narrow scopes, logging and privileged-account scrutiny.
Executive brief
The record October 29 Binance theft didn't start with a stolen key. According to Binance's incident report, attackers spent months working through developer tooling. They used a tampered Homebrew install, a fake job interview and then an internal AI tool to reach a wallet-signing service. Binance puts the loss at $6.34 billion. The FBI attributes the theft to North Korea's TraderTraitor group. Elliptic calls it 4.4 times larger than the Bybit hack. Binance says it has replenished 98% of affected assets, and about $2.85 billion is frozen.
Read the full section
The record October 29 Binance theft didn't start with a stolen key. According to Binance's incident report, attackers spent months working through developer tooling. They used a tampered Homebrew install, a fake job interview and then an internal AI tool to reach a wallet-signing service. Binance puts the loss at $6.34 billion. The FBI attributes the theft to North Korea's TraderTraitor group. Elliptic calls it 4.4 times larger than the Bybit hack. Binance says it has replenished 98% of affected assets, and about $2.85 billion is frozen. North Korea denies involvement.
What changed and event timeline
Tampered Homebrew hits a wallet engineer
A Wallet DevOps engineer installed a tampered Homebrew while setting up an AI coding tool. Binance replaced the device and rotated credentials, but the engineer's role had already been exposed (;).
Fake recruiters plant malware
Attackers posing as recruiters, reportedly on LinkedIn, ran two interviews. The second delivered a coding assignment containing obfuscated malware (;).
Internal AI tool used to move laterally
From the infected laptop, attackers used an internal AI tool to obtain wallet-team credentials and a container deployment token ().
Hot wallets drained
A malicious container and script hit the wallet-signing service. Unauthorized transfers ran from 20:05 to 23:56 UTC, and the last ETH transfer cleared at 00:10 UTC on October 30 ().
FBI names TraderTraitor
The FBI attributed the theft to North Korea and asked node operators, DeFi services and exchanges to block the laundering addresses ().
Report, TV interview, denial
Binance published its report and Teng appeared on CNBC. Kim Yo Jong called the attribution "a political attack" (;).
Capabilities and access
- No AI model is named. Neither the public "popular AI coding tool" nor Binance's internal AI tool is identified (CNBC).
- The internal tool's role is undescribed. Binance doesn't say whether it was an agent, a chat assistant or something with tool permissions.
- What the attackers ended up holding: credentials, a container deployment token and the ability to get the signing service to authorize transfers (BleepingComputer).
Read the full section
- No AI model is named. Neither the public "popular AI coding tool" nor Binance's internal AI tool is identified (CNBC).
- The internal tool's role is undescribed. Binance doesn't say whether it was an agent, a chat assistant or something with tool permissions. It only says the attackers used it "to gain control over" other engineers' access (Fortune).
- What the attackers ended up holding: credentials, a container deployment token and the ability to get the signing service to authorize transfers (BleepingComputer).
Technical analysis for researchers and developers
- Persistence: the malware dropped a
pyenv_executable into the macOS Homebrew directory and replaced the realpyenvwith a version that spawnedzshto run commands. - Signing: keys weren't extracted. A signer approved transactions it shouldn't have (Cointelegraph/Blockaid).
- EIP-7702: an EIP-7702 authorization gave a malicious contract partial execution rights over a hot wallet. That let theft continue after withdrawals were suspended (Binance report).
Read the full section
- Persistence: the malware dropped a
pyenv_executable into the macOS Homebrew directory and replaced the realpyenvwith a version that spawnedzshto run commands. Binance calls it custom 0-day malware (BleepingComputer). - Signing: keys weren't extracted. A signer approved transactions it shouldn't have (Cointelegraph/Blockaid).
- EIP-7702: an EIP-7702 authorization gave a malicious contract partial execution rights over a hot wallet. That let theft continue after withdrawals were suspended (Binance report).
- Reproducibility: no indicators of compromise (IOCs), malware hashes or details of the AI tool's permissions have been published.
Claims and evidence
- Loss of $6.34 billion and 98% replenished: this is Binance's own figure (report).
- Frozen funds: Elliptic verified $2.85 billion (44%), 94% of it stablecoins. Other outlets report about $3 billion (CNBC) or $2.5 billion (Fortune).
- Attribution: the FBI, Elliptic, TRM and Chainalysis all point to TraderTraitor.
Read the full section
- Loss of $6.34 billion and 98% replenished: this is Binance's own figure (report). Elliptic, working from on-chain data, puts the loss at $6.43 billion (Elliptic).
- Frozen funds: Elliptic verified $2.85 billion (44%), 94% of it stablecoins. Other outlets report about $3 billion (CNBC) or $2.5 billion (Fortune).
- Attribution: the FBI, Elliptic, TRM and Chainalysis all point to TraderTraitor. North Korea denies it.
- The AI-tool attack chain: this rests on Binance's account alone. No independent forensic corroboration exists yet.
Context and prior work
- Bybit precedent: in February 2025, $1.46 billion was stolen from Bybit, another TraderTraitor case that went through developer infrastructure rather than direct key theft (Elliptic).
- Earlier Binance hack: Binance lost $570 million in 2022 (NBC News).
- An ongoing campaign: Binance says it detected and stopped 57 other suspected North Korea-linked attempts in 2026 that used fake interviews and malicious developer tools (The Block).
Read the full section
- Bybit precedent: in February 2025, $1.46 billion was stolen from Bybit, another TraderTraitor case that went through developer infrastructure rather than direct key theft (Elliptic).
- Earlier Binance hack: Binance lost $570 million in 2022 (NBC News).
- An ongoing campaign: Binance says it detected and stopped 57 other suspected North Korea-linked attempts in 2026 that used fake interviews and malicious developer tools (The Block).
Limitations, safety and contested findings
- EIP-7702's role is disputed. Blockaid says it may have amplified the theft.
- AI laundering isn't shown. Elliptic found automated laundering but no proof that AI agents directed the transactions (CoinDesk).
- Accounts differ on who was compromised and when. BleepingComputer describes two additional employees (BleepingComputer).
Read the full section
- EIP-7702's role is disputed. Blockaid says it may have amplified the theft. Ambire's Ivo Georgiev says it made "little difference" but warns that leftover delegations are poorly understood (Cointelegraph).
- AI laundering isn't shown. Elliptic found automated laundering but no proof that AI agents directed the transactions (CoinDesk).
- Accounts differ on who was compromised and when. Binance says the October 20 step took Engineer A's credentials and token (report). BleepingComputer describes two additional employees (BleepingComputer).
- Funds still at large: about $3.25 billion in assets that can't be frozen remains under attacker control (Elliptic).
Business and practitioner implications
- Treat them as privileged lateral-movement paths: scope their credentials and tokens tightly, and log every tool action they take.
- Install developer tools from trusted sources. Pin and verify package-manager installs instead of following search-engine links.
- Fake interviews were the entry point here and in many of the 57 attempts Binance says it stopped.
Read the full section
- Internal AI tools need tight limits. Treat them as privileged lateral-movement paths: scope their credentials and tokens tightly, and log every tool action they take.
- Install developer tools from trusted sources. Pin and verify package-manager installs instead of following search-engine links.
- Watch recruitment-style approaches to engineers. Fake interviews were the entry point here and in many of the 57 attempts Binance says it stopped.
- Check what signers actually sign. Add transaction simulation and policy checks at the signer, and audit and revoke EIP-7702 delegations (Cointelegraph).
- Stablecoin issuers' freezes recovered the most. Tether and Circle froze stablecoins quickly, and that accounts for almost all of the money held so far.
The source trail.
Sources (12)
Binance co-CEO Richard Teng says hackers used fake job interviews, AI tool to steal $6.3 billion in crypto
Article text retrieved; extracted text may omit tables or interactive elements.
cnbc.comHackers behind $6.3bn Binance heist ‘used malware and bogus job interviews’
Related coverage; assess separately
theguardian.com