A Binance fake job interview, a tampered Homebrew installer and an internal AI tool carried attackers from engineers' laptops to the hot wallets drained of $6.34 billion on October 29, according to the exchange's November 3 incident report. The entry point was a recruiter and a coding test, not a protocol bug.
Key takeaways
- Binance traces the $6.34 billion theft to a tampered Homebrew install, a fake recruiter's coding test on a work laptop, and an internal AI tool.
- Credentials and a container deployment token from engineer machines launched the script that drained the hot wallets on October 29.
- An EIP-7702 delegation and the MPC wallet setup kept Ethereum transfers moving until 00:10 UTC on October 30.
- About $2.85 billion is frozen or intercepted; the 98% replenishment used replacement assets, not recovered funds.
What does Binance's November 3 report actually establish?
The report blames people and everyday developer tools, not a flaw in Binance’s code. Published November 3, 2026, it says a fake job-interview process and abuse of an internal AI tool helped attackers reach wallet infrastructure before the October 29 theft.
Attribution is not new: Hackread.com had already reported the FBI’s finding that North Korea was behind the theft, and we covered what the FBI attribution already asked companies to check. Co-CEO Richard Teng wrote on X: “We are committed to covering all hacked losses through our company funds. Your assets are safe.”
What the report adds is the route: three engineers’ devices over five months, ending with a container deployment token and stolen credentials.
How did a Binance fake job interview reach three wallet engineers?
Binance describes three stages, each disguised as ordinary developer work.
- June 2026. A wallet DevOps engineer searching for an AI coding tool downloaded a tampered Homebrew installation. Binance replaced the device and rotated credentials, but the attackers had already learned the engineer’s role and wallet-team connections.
- September 2026. A fake recruiter on a job-hunting platform approached Engineer B. The second interview ended with a coding assignment downloaded onto a work laptop; its repository swapped a legitimate pyenv file for a malicious one, letting the attackers run commands and contact a server they controlled.
- October 20. From Engineer B’s machine, the attackers used an internal AI tool to reach the devices of Engineer A and Engineer C. Engineer A’s computer held a container deployment token.
The report does not say how the June activity was spotted or whether anything flagged the pyenv swap before October 20. That detection gap is the part defenders should study.
Binance has not named the internal AI tool, its vendor or its permissions, or explained how it reached two other devices. Gina Cardelli, Director of Platform and Threat Intelligence at Fortra, framed the concern:
“While using a work computer for an external coding assessment warrants its own scrutiny, the larger concern is how that compromise enabled access to other systems and sensitive financial infrastructure.”
What drained the hot wallets on October 29?
On October 29 the attackers accessed Engineer C’s computer and used Engineer A’s stolen credentials to deploy a container and launch a malicious script. Binance lists these transfers:
- 233.46 million XRP from five hot wallets, 20:05 to 20:09 UTC
- about 970,500 SOL and 44.2 million OP on Solana and Optimism
- 18,270 BTC
- 2,961.9 ETH, broadcast earlier and settled at 23:56 UTC
Suspending withdrawals could not immediately stop that last transfer because of EIP-7702, an Ethereum mechanism that lets an account delegate certain execution rights to a smart contract. An attacker-controlled contract gained partial execution rights over a Binance hot wallet without the private key ever being exposed, and the on-chain authorization survived the withdrawal pause.
Binance’s multi-party computation (MPC) wallet splits signing between separate parties so one stolen key cannot drain funds. The same design left no single private key to revoke the delegation quickly. “These challenges extended the time required to fully contain the unauthorized asset movements,” the report says. Binance cleared the delegation at 00:10 UTC on October 30.
Does 98% replenished mean Binance recovered the stolen crypto?
No. Binance says it replenished 98% of affected token assets by October 31 with replacement assets: customer balances refilled, not stolen coins returned. Roughly $2.85 billion was frozen or intercepted as of November 3, subject to reconciliation and price changes. Against the $6.34 billion theft-time figure, that is under half.
Binance says it rebuilt affected systems, replaced compromised devices and tightened access controls. The investigation is ongoing, and independent cybersecurity firms will review its findings.
What should crypto firms, fintechs and EMIs test now?
Test whether one developer laptop can reach wallets, payment systems or production deployment. The recruiter-and-repository approach works against any company whose engineers hold deployment tokens.
For EU firms this is also a compliance matter. DORA has applied since January 17, 2025, and covers e-money institutions and crypto-asset service providers authorized under MiCA, including those supervised by CySEC in Cyprus. Firms must test their ICT controls, and designated entities must run threat-led penetration tests. Binance is not isolated: in February 2025 attackers took about $1.5 billion from Bybit, a theft the FBI also attributed to North Korea.
- Coding tests. Run recruiter repositories only in a disposable VM with no SSO session, VPN or company credentials.
- Dev tool installs. Allow-list package managers and AI coding tools; alert on changes to Homebrew or pyenv files.
- Deployment tokens. Make container and registry tokens on laptops short-lived, narrowly scoped and pipeline-only.
- Internal AI tools. Map what each assistant can reach on other machines; treat it as a privileged account.
- On-chain revocation. Rehearse revoking delegations and keep MPC share holders reachable around the clock.
- After a compromise. Ask what the intruder learned about your staff and tooling.
We routinely find long-lived registry and orchestrator tokens in shell history, dotfiles and cached CLI configs on developer laptops. A social engineering and phishing assessment shows which engineers would run a recruiter’s repository; DORA penetration testing from one developer endpoint shows how far an attacker gets, with evidence a supervisor can review.
FAQ
Did a fake recruiter trick a Binance engineer?
Yes. Binance says a fake recruiter had an engineer download a malware-laced coding assignment onto a work laptop.
How did an internal AI tool help the Binance attackers?
Binance says it let attackers reach two more wallet engineers' devices on October 20, but has not named the tool or explained how.
Why could Binance not stop the Ethereum transfers right away?
The EIP-7702 delegation lived on-chain, so pausing withdrawals did not revoke it, and the MPC setup left no single key to cancel it quickly.
Was 98 percent of the Binance hack recovered?
No. Balances were refilled with replacement assets; about $2.85 billion was frozen or intercepted as of November 3.
If an engineer’s laptop or deployment token may be compromised, our crypto hack incident response team can help scope and contain the access before funds move.
Tell us what you're running
Scoping is free. We reply within one business day, and under 30 minutes for active incidents.
