Binance published its first incident report on Tuesday, and the $6.3 billion theft did not start with a zero-day. It started with a job ad. A Binance engineer looking for new work took an interview, met a “CEO” over video, and downloaded a take-home coding test. That test was the door.
The Report in One Line
According to the account Reuters carried on NBC News, the attackers spent five months on the way in and nine days on the way out. Binance co-CEO Richard Teng put it plainly on X: “This wasn’t one mistake or one breach.” He is right, and that is the problem.
Five Months, Four Steps
We laid out the chronology from the report as The Block summarized it, and counted the gaps ourselves.
| When | What happened | Gap to next step |
|---|---|---|
| June 2026 | A wallet DevOps engineer installs a tampered Homebrew package while setting up an AI coding tool. Binance catches it, swaps the laptop, rotates credentials. The engineer’s role and teammates are still exposed. | about 3 months |
| September 2026 | A second engineer, job hunting, interviews with a fake company, including a video call with its “CEO”, and downloads a malicious code repository as the assignment. | weeks |
| October 20 | From that machine, the attackers use an internal AI tool to take over two wallet developers’ computers. One holds a container deployment permission. | 9 days |
| October 29 | Using those stolen credentials, they deploy a container and run the script that drains the wallets. | 0 |
Read the first row again. Binance won the June round. It cleaned the device and changed the passwords. What it could not take back was the map: who works on the wallet team and who sits next to whom. The September recruiter knew exactly which engineer to call.
The Interview Is the Exploit
This playbook is not new. The FBI has blamed a North Korean group, and fake recruiters with poisoned coding tests are that group’s signature move. Pyongyang, for its part, called the claim absurd. Kim Jong Un’s sister went further and called it a “grave political provocation.”
Here is the part that should embarrass the industry. Binance says it blocked 57 suspected North Korea-linked attacks this year, many using the same tactics. So the tactic was known. The engineers were targets. And a work laptop still ran a stranger’s homework.
The AI Tool Did the Walking
The new detail is the internal AI tool. The attackers did not need to hand-craft their way from one laptop to the next. They used Binance’s own assistant to reach two more engineers’ machines. Companies have spent two years wiring AI agents into everything with broad access, because broad access is what makes them useful. It is also what makes them a hallway with every door open.
We think this is the real story, and it is bigger than one exchange. An agent that can act across colleagues’ devices is a privileged account. Nobody would hand a contractor that reach on day one. Plenty of firms hand it to a chatbot.
The Money
Binance says it has frozen or intercepted about $2.85 billion and replenished 98% of affected customer assets, and it says every customer who lost funds will be repaid. By our math, the frozen share is roughly 45% of the $6.3 billion taken. The rest is somewhere the exchange cannot reach, and Binance is covering that hole from its own balance sheet. Withdrawals began reopening in phases early Tuesday, and Binance says deposits have since outpaced them. We covered how the funds left in under four hours last week.
What Changes Now
Binance says it has closed the entry points, rebuilt systems, tightened device controls and commissioned an independent review. “This should not have happened,” it wrote. Correct.
The fix that matters is unglamorous. Engineers with keys to the vault should not run interview assignments on the machines that touch the vault, and AI agents should get the permissions of an intern, not a sysadmin. The hackers needed patience, a fake company and one helpful bot. Every exchange still hiring engineers should ask how many of those it is offering for free.