NEWS
Binance Caught a June Laptop and Still Lost $6.34 Billion
Binance caught a tainted June laptop, then lost $6.34 billion after a fake job interview and its own AI tool reached the wallet signer.
Binance co-CEO Richard Teng said hackers spent months inside the world’s largest crypto exchange before they pulled $6.34 billion from its hot wallets on October 29. The first foothold was a tainted developer install in June that Binance caught, replaced, and treated as contained.
A fake job interview in September and the firm’s own internal AI tool finished the job. Teng said the attackers did not need a single employee laptop as one point of failure. As of October 31, Binance said it had replaced 98% of the affected tokens from company funds.
Four Minutes, Five Hot Wallets
The drain started at 20:05 UTC. Five hot wallets sent 233.46 million XRP to an attacker-controlled address by 20:09 UTC. Solana and Optimism wallets then sent about 970,500 SOL and 44.2 million OP. After an internal alert on the large transfers, a hot wallet sent 18,270 BTC.
Binance says the attacker had unauthorized use of an internal wallet signing service, so the transfers sat outside the normal withdrawal path. No private keys were found to have leaked. The signer did the work.
THE OCTOBER 29 TRANSFERS
| Asset | Amount | When it moved |
|---|---|---|
| XRP | 233.46 million, from five hot wallets | 20:05 to 20:09 UTC |
| SOL | about 970,500 | after the XRP burst |
| OP | 44.2 million | with the Solana wallets |
| BTC | 18,270 | after the internal alert |
| ETH | 2,961.9 in the last hop | 23:56 UTC |
The last unauthorized transfer, 2,961.9 ETH, finalized on-chain at 23:56 UTC after sitting pending. Binance says it saw no further unauthorized moves after that. At 00:10 UTC on October 30 it pushed a new authorization from the Binance14 hot wallet to the zero address and cleared the hostile delegation.
On November 3 the exchange published its initial findings on the October theft and said some technical detail would stay confidential so copycats could not reuse it.
— Binance (@binance) November 3, 2026
Binance Caught the June Laptop and Still Lost the Team Map
Engineer A, on the Wallet DevOps team, searched for a popular AI coding tool and downloaded a tampered Homebrew install. Binance’s security team spotted the anomaly, replaced the device, and rotated the related credentials.
That was not enough. By then the attacker knew Engineer A’s role and who sat with him on the wallet infrastructure team. Teng later put it in plain terms: the attackers spent months building their way in, and a swapped laptop did not wipe that map.
Fake Homebrew pages in search ads were already a known Mac lure. In May, SANS Internet Storm Center handler Brad Duncan described malicious ads that impersonated Homebrew and pushed MacSync Stealer. Binance pointed at that style of tampered install for the June download. It did not name the June payload as MacSync, and the September implant was a separate 0-day its endpoint tools missed.
Replacing a machine closes a session. It does not unsay an org chart. The people who could sign wallet moves were now a target list, and the next approach did not need Engineer A’s new laptop.
A Fake CEO, a Coding Test, a Work Computer
In September, Software Engineer B, whose job-platform profile mentioned Binance, was contacted through that same legitimate site by someone posing as a Project Director. A first-round live video followed with a purported HR representative, who shared a social account packed with personal photos and videos to look real. The second round was on a popular chat app with someone claiming to be CEO of a company that does not exist.
Near the end of that chat, Engineer B was told to download an “assignment” onto his work computer. The repository ran code during setup. It replaced a legitimate pyenv binary under Homebrew with a 3,414-byte malicious copy, rebuilt the symlink, and spawned zsh to talk to an attacker server. Binance called it 0-day malware. Endpoint tools did not flag it, and the operator wiped traces.
Chief security officer Jimmy Su said the first contact came as a Project Director on a real job platform, then a live HR video, then a CEO round that ended in the homework. A coding test on a work laptop is not a side channel. If that laptop can hold a deploy token, the hiring pipeline sits inside the wallet perimeter.
THE FOUR-MONTH PATH IN
- June 2026: Engineer A installs tampered Homebrew while hunting an AI coding tool. Binance replaces the device and rotates credentials. The wallet team is already exposed.
- September 2026: Engineer B runs a fake-interview assignment on a work computer. Hidden malware swaps pyenv and opens a channel.
- October 20, 2026: From Engineer B’s machine, the attacker uses an internal AI tool to take over Engineer A and Wallet Software Engineer C, then finds a container deployment token on A’s computer.
- October 29, 2026: Between 17:15 and 19:56 the attacker logs onto Engineer C’s computer, uses A’s stolen credentials, deploys a container, and launches the script that hits the signing service.
Teng said the September interviews ended in a coding exercise with hidden malware built to evade security, and that the attackers then moved through internal AI tools to the system that authorized wallet transactions.
The Internal AI Tool Became the Springboard
Binance has not said how the internal AI tool was steered. It has said what the tool did on October 20. From Engineer B’s compromised computer, the attacker used it to gain control of Engineer A and Engineer C. On A’s machine sat a container deployment permission token.
Nine days later the attacker logged into Engineer C’s computer, reused A’s credentials, deployed a container, and triggered the script. That hop turned two social-engineering wins into a production move. The AI assistant was supposed to help engineers work. On that path it helped the operator reach the people who could deploy into wallet systems.
After the theft Binance rebuilt the affected internal AI tool and its access controls, rebuilt the wallet system in a new environment, replaced affected devices, and decommissioned credentials and tokens tied to the three engineers. It also ran extra security scans across employee devices. The tool that carried the attacker had to be torn out and stood up again before withdrawals could even be discussed.
Pausing Withdrawals Did Not Stop the Drain
Once inside the signer, the attacker used Ethereum’s EIP-7702. That feature lets an account set code on an Ethereum account and delegate execution to a smart contract without exposing the private key. The attackers submitted 50 signing transactions to set those delegations. After that, the contract could keep moving assets even when Binance had halted normal withdrawals.
WHY THE DELEGATION OUTLIVED THE HALT
- On-chain rights: EIP-7702 authorizations live on the chain, not in Binance’s withdrawal queue, so a halt does not cancel them.
- Fifty signatures: The operator packed signing transactions to set malicious delegations on a hot wallet.
- MPC delay: The hot wallet uses multi-party computation, so no single private key could revoke the code. The team had to build a special revoke path.
- Zero-address clear: At 00:10 UTC on October 30, Binance14 authorized the zero address and wiped the delegation.
Su said containment ran until that 00:10 UTC revoke because the MPC setup blocked a one-key kill. The final ETH hop had already been broadcast and only later settled. Partners spent the same night freezing tokens they still controlled. Tether CEO Paolo Ardoino said his firm froze more than 1.567 billion USDT. Circle CEO Jeremy Allaire said Circle froze more than 800 million USDC. Binance later put the combined freeze-or-intercept total at $2.85 billion, subject to price moves and reconciliation. Coinbase blocked transfers to compromised wallets and offered direct help.
We’re also getting an independent expert to review everything that we have done, and we’ll keep strengthening our defenses as the investigation continues.
Richard Teng, Binance co-CEO, on Squawk on the Street
Binance Blocked 57 North Korea Cases in 2026
The FBI named North Korea as responsible on October 31 and tagged the activity TraderTraitor. It said the actors were converting stolen assets mainly into ether, then toward DeFi and instant swaps, and it published addresses for exchanges and node operators to block. Teng did not himself pin the job on Pyongyang. He pointed to that FBI finding.
TraderTraitor is the label the FBI used for the about $1.5 billion Bybit theft in February 2025 and the about $308 million DMM Bitcoin theft in 2024. The method is familiar: a recruiter persona, a coding task, then the engineer’s sessions and the software that builds or signs transfers. A separate North Korean cluster, Contagious Interview, uses the same job-test lure on a wider set of developers. Security firms warn that a model built only for that cluster will miss TraderTraitor’s slower, more selective path into privileged wallet staff.
Binance says its team detected and prevented 57 suspected North Korea-linked cases in 2026, including fraudulent interviews, poisoned developer tools, bad packages and browser extensions, and fake video-call apps. On October 27, two days before the drain, the exchange said it had blocked several Contagious Interview-style attempts that week, with no systems compromised and no assets lost.
WHAT THOSE 57 CASES LOOKED LIKE
- Fake interviews: Recruiter contact, video rounds, then a test that runs code on the target’s machine.
- Poisoned tools: Search-bar installs and lookalike developer packages, including Homebrew-style lures.
- Fake meeting apps: Video-conference bait used to drop remote-access malware.
- The miss: The September implant on Engineer B was already in place when the October 27 warning went out.
Stopping 57 attempts is a real defensive record. It is also the setup for the one that paid. The October 27 note described a week of blocked lures. It did not describe Engineer B’s homework from September, or the wallet-team map taken in June. Kim Yo Jong, a senior North Korean official, later called the FBI’s attribution a political provocation. The bureau has not withdrawn it.
The Stolen Coins Are Still Moving Through Meme Tokens
Binance said it would absorb the loss, not pass it to users, and that it had set aside more than 100% of the funds required. As of October 31, 98% of the impacted token assets had been replaced, checkable on its Proof of Reserves page. The rest, it said, are less liquid tokens still being bought. BTC, ETH, USDT, BNB, SOL, USDC, XRP, USD1, RLUSD, and ZEC were listed as fully backed.
Withdrawals restarted in phases at 06:00 UTC on November 1. By 12:36 UTC all 15 networks in the first wave were open. From 06:00 to 15:30 UTC the exchange processed $4.649 billion in withdrawals and $1.01 billion in deposits, a net outflow of about $3.64 billion. That was 2.1% of $171 billion in assets under management on the October 28 proof-of-reserves snapshot. Further tokens were still being reopened on November 3 and November 5 after extra checks.
The frozen slice and the replaced slice are not the same money. Company reserves filled customer balances. Issuers and chains locked what they could still reach. A large remainder sits in bitcoin, ether, and other units no issuer can freeze by decree. The FBI asked THORNode operators, RPC nodes, instant exchanges, and DeFi desks to block listed addresses anyway.
On November 9, Elliptic researcher Dr. Tom Robinson said launderers had started minting six disposable NEAR meme tokens to break the on-chain link between stolen wallets and cash-out wallets. Between November 5 and November 7, FUK, OLCCL, MEILI, MMLI, DABI, and SINU each got a NEAR pool. About 117,000 NEAR, roughly $430,000, went through. Each token cost about $90 to create. Outside buying of FUK was under 1% of its volume. None of the six traded after November 8.
The sums are small next to $6.34 billion. Elliptic also said about 11.8 million NEAR, about $43.7 million, from the theft had not yet moved, and that the same cheap pools could carry more. Teng said Binance is still working with law enforcement and industry partners to trace and freeze what remains. The independent review of the June miss, the September interview, and the AI-tool hop has not been published.
A swapped laptop in June closed one door. The people behind that door were already named, and the next assignment ran on a work machine that could still reach the signer.
Disclaimer: This article is news reporting and analysis of a security incident and recovery at a cryptocurrency exchange. It is for information only and is not investment, trading, legal, or cybersecurity advice, and it is not a recommendation to buy, sell, hold, or move any token or to use any particular wallet, exchange, or freeze process. Readers who hold crypto or who may be affected by frozen addresses, proof-of-reserves figures, or withdrawal status should consult a licensed financial adviser and, where relevant, a qualified security professional before acting. Amounts stolen, frozen, and replaced, plus attribution and open investigations, reflect the company, FBI, and analytics-firm statements cited here and can change as tracing and reviews continue.
-
BUSINESS3 months agoConsumer Sentiment Falls to 51.7 as Future Outlook Darkens
-
GAMING3 months agoTake-Two Subpoenas Microsoft While GTA 6 Preorders Soar
-
NEWS3 months agoPluto’s Heart Glacier Still Pushes Liquid Nitrogen Upward
-
NEWS3 months agoThe Extra Heat Month Hits Children Where Care Is Thinnest
-
ENTERTAINMENT3 months agoNetflix Weighs Hosting Peacock and Fox One in Its App
-
NEWS3 months agoFDA Clears Rasonque and Widens Who Can Take It
-
NEWS3 months agoUMMC Will Rebuild 30-Year-Old Cancer Labs With $2.4 Million
-
GAMING3 months agoGTA 6’s 80-Hour Run Counts Goals That Change the Story
