Binance's $6.3B Heist: Fake CEO Interview to Internal AI

Thumbnail image of golden cryptocurrency flowing out of a dark digital vault

The Fake Company That Slowly Poked Holes in Binance

✦ The Binance Hack at a Glance

✔ Date of the incident: October 29, 2026
✔ Infiltration began: June 2026 (infected through a tampered Homebrew)
✔ Amount stolen: About $6.3 billion (17 hot wallets, 9 blockchains)
✔ Attack path: Fake interview → internal AI tool → container and wallet signing service
✔ Binance's response: Replenished about 98% of affected customer assets with its own funds (November 4)

A developer at Binance was thinking about changing jobs. Then a fake company's Project Director contacted the developer first on a job platform.

The developer's first interview was a live video call with a purported HR representative, and the second one, over a messaging app, was with the purported CEO of a fictitious company.

At the end, the CEO reportedly told the developer to download a coding assignment. The developer ran the assignment on a company computer, and it had malicious code inside.

A month later, on October 29, billions of dollars' worth of crypto drained out of Binance's online wallets.

✦ Binance Infiltration Timeline

June 2026
Employee A first compromised through a tampered Homebrew
September 2026
Employee B installs a malicious repository through the fake interview
October 20, 2026
Attacker reaches A's and C's systems through the internal AI tool and finds a deployment token
October 29, 2026
About $6.3 billion moves out of 17 hot wallets on 9 chains
October 29, 2026, 23:56 UTC
Last unauthorized transfer of 2,961.9 ETH confirmed
October 31, 2026
FBI announces North Korea is responsible
November 3, 2026
Binance announces $6.34 billion in impact
November 4, 2026
Binance replenishes 98% of customer assets with its own funds
November 5, 2026, 07:37 UTC
About $3.2 billion still sits in the attacker's wallets

Binance counted the total impact of the incident at $6.34 billion. At first glance it looks like the attack suddenly began that very day, but that's not what happened.

A developer's computer had already been exposed back in June, and by September another employee had been infected through a fake recruitment interview.

And in October, it went through an internal AI tool and developer permissions to reach the wallets' transaction approval system. It was a meticulous plan.

First Target: Planting Malware on a Binance Employee

Employee A on Binance's Wallet DevOps team was searching for an AI coding tool and downloaded a tampered Homebrew installer through a search ad. (Homebrew is a package manager for installing and managing developer programs on macOS.)

Binance's security team spotted the anomaly, swapped out A's device and changed the related credentials. But the attacker already knew what A did on the wallet infrastructure and who A worked with.

Second Target: A Fake Interview That Started on a Real Job Site

✦ The Fake Interview Came in Four Steps

1Contact on a job platform
A fake Project Director approaches B after seeing B's Binance experience
2First interview
Live video call with a fake HR rep, with social media photos and videos building trust
3Second interview
Messenger interview with the purported CEO of a fictitious company
4Coding assignment
B downloads and runs the assignment repository and gets infected with malicious code

A few months later, another developer, B, got a message. The sender posed as a Project Director on a real job platform and approached B after checking the Binance experience on B's profile.

The first interview was a live video call with someone posing as an HR representative. The other side reportedly even showed a social media account with personal photos and videos, building trust the way a real person would.

The second interview moved to a messaging app, and this time someone claiming to be the company's CEO showed up.

Near the end, B was asked to download and run a coding assignment, and since that's a common step in developer hiring, it would've been hard to get suspicious.

The assignment contained a repository with malicious code. When B ran the setup, the malware kicked in and opened a channel to an external server controlled by the attacker.

The malware deleted the legitimate executable of pyenv, the tool developers use to manage Python versions, and replaced it with a tampered file that mimicked its name and role.

A 3,344-byte file was swapped for a 3,414-byte one that runs commands and connects to an external server. Unfortunately, Binance's endpoint security system at the time failed to detect the tampering.

〈How a fake job interview led to Binance's $6.3B hack〉
* From the Professor Zero YouTube channel.

The Real Attack: Through the Internal AI Tool to the Wallet's Approval Power

On October 20, the attacker used B's computer and Binance's internal AI tool to get into the systems of A, the wallet operations employee, and C, a wallet software developer. The attacker even found a container deployment permission token in A's work system.

On October 29, the attacker got into C's computer, used the credentials taken from A to deploy a container, and ran a malicious script.

That script reached the “wallet signing service,” Binance's internal system that attaches approval signatures to transactions sending crypto to other addresses.

Instead of the regular customer “withdrawal process,” the attacker created transactions through this “internal approval system” and took the money out.

Good to Know
What are containers and deployment permission tokens?

A “container” packs a program and the files it needs into a separate environment so it can run on its own, and a “deployment permission token” works like an access pass for putting those environments onto a company's infrastructure.

✦ How Much Was Stolen?

XRP233.46 million
From 5 hot wallets in 4 minutes
SOLAbout 970,500
OPAbout 44.2 million
BTCAbout 18,270

In the end, 233.46 million XRP moved from five Binance hot wallets to the attacker's address in just four minutes. Other assets followed: about 970,500 SOL (Solana), about 44.2 million OP (Optimism), about 18,270 BTC (Bitcoin), and more.

Bitquery, a blockchain data analytics firm, traced the overall movement of funds and counted about $6.3 billion leaving 17 hot wallets across 9 blockchains.

Good to Know
What's a hot wallet?

To move assets fast whenever customers deposit or withdraw, crypto exchanges run wallets that are connected online. These are called hot wallets.

This attack went right after the development team that manages those wallets.

What made this attack especially tricky was Ethereum's EIP-7702 feature. It helps a regular wallet account run the code of a specific smart contract from the account itself.

In other words, EIP-7702 is a feature built to make wallets more convenient to use, but the attacker abused it to link some of the execution rights of Binance's hot wallets to a smart contract the attacker controlled.

Once the permission was recorded on the blockchain, it didn't go away even after Binance halted withdrawals.

On top of that, the hot wallets run on MPC (Multi-Party Computation), a setup where several participants split the calculation to approve transactions, so the permission couldn't be wiped out right away with a single key either.

Because the attack was so hard to counter, Binance ended up having to create a separate on-chain transaction to revoke the permission. The last unauthorized transaction, 2,961.9 ETH, was confirmed on the blockchain at 23:56 UTC.

That was almost four hours after the attack began. Investors who had deposited crypto with Binance spent all that time on edge.

〈Concept corner: what a hot wallet is〉
* From the Bitpanda Global YouTube channel.

Trust in Crypto Exchanges Is Crashing

✦ Four Numbers, Four Different Meanings

About $6.34 billion
• Impact of the incident, as announced by Binance
• Basis: initial report, November 3
About $2.85 billion
• Amount frozen or blocked
• Basis: announced November 3
About 98%
• Share of customer assets Binance replenished with its own funds
• Basis: announced November 4
About $3.2 billion
• Estimated balance left in the attacker's wallets
• Basis: November 5, 07:37 UTC (Bitquery)

Binance put the incident's impact at about $6.34 billion and said about $2.85 billion was frozen or blocked from moving. On November 4, the company announced it had topped up about 98% of the affected assets with its own funds.

Investors got a bit of breathing room, but now you can't even count on Binance being safe.

Where the stolen crypto still sits can be traced through blockchain data. Bitquery's analysis found that, as of 07:37 UTC on November 5, about $3.2 billion worth of crypto was still in the attacker's wallets.

The Federal Bureau of Investigation (FBI) announced on October 31 that North Korea was responsible for the theft and called the related cyber activity TraderTraitor.

North Korea pushed back, calling the FBI's announcement a political provocation in a statement issued under the name of Kim Yo Jong, the sister of State Affairs Commission Chairman Kim Jong Un.

Either way, trust in crypto exchanges is hitting the floor. Big exchange hacks keep happening, so investors can only pray, “Please don't let the next hacked exchange be the one I use...”

That's crypto's fatal weakness. Given the nature of digital assets that have no physical substance, it looks like hacks will keep coming.

That's all for this post. See you next time.

Related posts

No comments:

No comments yet. Want to leave the first one?