Build · founder · 6 min read
Binance's $6.3B Heist Started With a Fake AI Coding Tool Download
Attackers drained about $6.3B from Binance after an engineer grabbed a tampered AI coding tool installer. What happened, and the habits that would have helped.
On November 3, Binance’s co-CEO laid out how roughly $6.3 billion in crypto left the exchange’s hot wallets. The theft is the headline. The entry point is the part that matters to you: an engineer searched for a popular AI coding tool and downloaded a tampered installer.
Some coverage has called this a “vibe coding” hack. That framing overreaches, and we’ll be precise about it below. But the pattern is one every founder using AI tools should recognize.
What happened, in order
The account below comes from Binance’s own write-up as reported by SecurityWeek and Tom’s Hardware.
June. A wallet DevOps engineer searched for a popular AI coding tool and installed a tampered version through Homebrew, a common Mac package installer. Binance caught it, replaced the laptop and rotated credentials. By then the attackers had already learned who sat on the wallet team.
September. A second engineer was contacted through a job-hunting platform by someone posing as a project director. Two interviews followed, one with a fake HR rep and one with a supposed CEO of a company that doesn’t exist. Then came the ask: download a “coding assignment” onto a work computer. Setting it up ran hidden code that swapped a legitimate developer tool component for a malicious copy. Endpoint protection didn’t flag it.
October 20 onward. The attackers used the infected machine and an internal AI tool to take over the first engineer’s system and a third wallet engineer’s system. The reporting doesn’t explain how the AI tool was used. A container-deployment token stored on one machine let them deploy their own container and run a script.
The theft. With access to the internal wallet signing service, they moved XRP, SOL, OP and BTC out of hot wallets. They also abused an Ethereum feature (EIP-7702) to give an attacker-controlled contract partial control over a hot wallet. Binance says pausing withdrawals couldn’t stop that, because the on-chain authorizations ran independently of its withdrawal systems.
The FBI attributes the attack to North Korea’s TraderTraitor group. North Korea denies it.
What the AI angle really is
Be careful here. Neither SecurityWeek nor Tom’s Hardware says anyone was vibe coding, or that an AI coding agent was hijacked and acted on its own. Futurism’s headline makes the vibe-coding claim; its own reporting doesn’t back it up. Blockchain analytics firm Elliptic found automation in the laundering but no sign of AI agents making decisions.
The real AI connection is narrower and more useful to you:
- AI coding tools are now a lure. People are searching for them constantly, which makes “popular AI coding tool” a great phishing and fake-installer topic.
- Internal AI tools are a stepping stone. An AI tool wired into company systems is another door with access behind it.
So the lesson isn’t “AI got hacked.” It’s that the oldest trick in the book, getting someone to run a file, now has a very hot bait.
Why this matters if you’re not Binance
You don’t have a $6 billion hot wallet. You probably do have a laptop with a Stripe key, a database password, a deploy token, or a Supabase service key on it. Attackers who go after a crypto exchange for months use the same entry moves that work on a five-person startup. The difference is patience.
Habits that would have helped
Install tools only from the maker’s own site or docs. Don’t search “Cursor download” or “Claude Code install” and click the first result. Go to the company’s domain you already know, or the link from their official documentation. Search ads and lookalike pages are how the June engineer got caught.
Treat any “coding assignment” or “take-home” as untrusted code. If a recruiter, client or stranger sends a project to run, open it in a throwaway cloud environment or a separate machine with nothing valuable on it. Never on the laptop that holds your keys.
Keep deploy tokens and API keys off your daily machine where you can. In the Binance timeline, a stored container-deployment token turned one infected laptop into a way to run code elsewhere. Use short-lived tokens, and store secrets in your host’s settings rather than a file on your desktop. Our guide on env files and coding agents covers the basics.
Rotate everything after an incident, then assume it wasn’t enough. Binance replaced the device and credentials in June and it still wasn’t sufficient, because the attackers already knew the team. If something suspicious ran on your machine, rotate keys and also ask what they learned: who you work with, which accounts you use, what you can reach.
Limit what your internal AI tools can touch. If you’ve wired an agent or chatbot into your database, billing or deploy pipeline, give it the narrowest access that still works. Read-only where possible. See what your agent is allowed to touch.
Be suspicious of friendly strangers who want you to run something. A polished interview process, a believable LinkedIn-style profile and a company website can all be faked. The ask to run code on your own machine is the tell.
What we don’t know yet
Binance hasn’t named the internal AI tool or explained how it was used. Independent security firms are still reviewing the incident, so details may change. We’ll update this guide if the picture shifts.
Bottom line
The most expensive crypto theft on record began with a download and a fake job. If you build with AI tools, your version of that story is shorter: someone gets you to install the wrong thing. Download from the source, run unknown code somewhere disposable, and keep your keys off the machine you browse the web on.
Related guides
founder · 8 min read
10 Apps Non-Technical Founders Built With Vibe Coding
Real examples of SaaS products, marketplaces, and tools built without code: what they built, which tools they used, and what it cost.
founder · 8 min read
Researchers put a virus in an agent's memory file. It spread to the next agent.
New Anthropic/EPFL research says AI agents can pass self-replicating instructions through files like CLAUDE.md. The fix is one paragraph.
founder · 9 min read
Your Agent Can Now Spend Your Money. Nobody Can Prove You Said Yes.
AWS shipped autonomous agent payments this month. The infrastructure works. The paper trail that would settle a disputed charge doesn't exist yet.
Enjoying this guide?
Get weekly practical guides, plus tool updates and implementation playbooks.