The Binance heist began with a fake job interview. North Korean hackers posed as recruiters, convinced a Binance engineer to download a malicious coding assignment, and used that foothold to steal about $6.34 billion on October 29, 2026. Treat any job offer that asks you to run code on a work computer as an attack.
What Happened in the Binance Heist?
Attackers moved funds across several blockchains through Binance’s wallet signing service, bypassing the normal withdrawal process. The FBI attributes the theft to North Korea, naming the state sponsored group TraderTraitor, which is also tracked as Lazarus Group, Jade Sleet and APT38. CISA documented the same group’s playbook against blockchain companies in advisory AA22-108A, years before this attack. Binance disclosed on November 3, 2026 that fake job interviews started the intrusion.
How Did the Fake Job Interview Work?
A person posing as a Project Director at a fictitious company contacted a software engineer on a legitimate job platform. The engineer’s profile mentioned past Binance experience, which made the target worth the effort. Two interviews followed:
- Interview one: a fake HR representative held a live video call and shared a social media account filled with personal photos and videos to build trust
- Interview two: on a chat app, the interviewer told the engineer to download a coding assignment from an online code repository
The assignment installed previously unseen custom malware that antivirus tools did not detect. It replaced the legitimate pyenv executable in the macOS Homebrew directory with a malicious version that ran commands from an attacker controlled server. The engineer ran it on a work computer, and that decision opened the door to everything that followed.
How Did One Engineer Lead to the Binance Heist?
By October 20, 2026, the attackers had used the compromised computer and an internal AI tool to take over two more engineers who worked on wallet infrastructure. They stole credentials and a container deployment token. Nine days later, on October 29, they used those credentials to deploy a malicious script, reach the wallet signing service and move funds across multiple blockchains within minutes.
- An attacker poses as a recruiter and contacts an engineer
- The engineer runs a malicious coding assignment on a work computer
- Custom malware evades antivirus and gives the attacker control
- The attacker abuses an internal AI tool to compromise two more engineers
- The attacker steals credentials and a container deployment token
- The attacker deploys a malicious script and reaches the wallet signing service
- Funds move across several blockchains before anyone stops the transfers
Why Did EIP-7702 Let the Attack Continue After Withdrawals Stopped?
Binance suspended withdrawals, but the attackers had already abused Ethereum’s EIP-7702 feature. EIP-7702 lets a wallet delegate control to contract code, so the attackers kept stealing through on chain delegation even though Binance had closed the normal withdrawal path. The lesson for defenders is plain. Halting transfers does not remove an attacker’s access, so incident response must revoke access and rotate keys as separate steps.
How Much Did Binance Lose and Recover?
Binance puts the impacted value at about $6.34 billion. As of November 3, 2026, about $2.85 billion in stolen assets was frozen or intercepted. Binance says it replaced 98 percent of the impacted token assets by October 31. That figure covers impacted tokens, and neither source states what share of the total theft it represents. The FBI says the attackers are mainly converting the stolen funds to Ethereum and expects more laundering through DeFi and swap services.
Is the Binance Heist Part of a Larger North Korean Pattern?
Yes. Binance says the tactics closely mirror two known North Korean campaigns, Contagious Interview and Operation Dream Job. Both use fake recruiters and fake hiring tests to get malware onto developer machines. The target changed, but the method did not. Attackers go after people with access, and engineers who hold keys and tokens make the best targets.
How Can Companies Prevent a Fake Job Interview Attack?
- Ban take home coding tasks on work computers and use a separate device for interviews and assignments
- Tell every engineer that a recruiter who asks them to run code is a threat, however real the profile looks
- Keep deployment tokens and signing credentials off laptops
- Limit what internal AI tools can access, because attackers used one to move between engineers
- Monitor changes to account permissions and delegation, not only outgoing transfers
- Scan developer devices for tampered tools, such as replaced package manager files and unexpected shell launches
- Revoke access and rotate keys as two separate steps during an incident
Binance rebuilt its wallet system and AI tool after the attack, replaced devices, removed engineers’ credentials, scanned employee devices and brought in independent security firms.
What Should Security Teams Do After the Binance Heist?
Test the human path into your systems, not just the network. Our team runs penetration testing and vulnerability assessments that show how far an attacker gets once one engineer’s computer falls, and our PTaaS platform keeps that testing running between audits. Our 2026 Mid Year Threat Pattern Report shows how quickly attackers turn a new foothold into damage.
Key Takeaways
- The Binance heist stole about $6.34 billion on October 29, 2026, and it began with a fake job interview
- The FBI attributes the attack to the North Korean group TraderTraitor
- A malicious coding assignment gave attackers a foothold, and an internal AI tool and a deployment token spread it
- Binance reports $2.85 billion frozen or intercepted and 98 percent of impacted tokens replaced
- Never run recruiter supplied code on a work computer
Frequently Asked Questions About the Binance Heist
What was the Binance heist?
The Binance heist was a theft of about $6.34 billion in digital assets on October 29, 2026. Attackers reached Binance’s wallet signing service after compromising engineers through a fake job interview.
Who did the Binance heist?
The FBI attributes the attack to TraderTraitor, a North Korean state sponsored group also tracked as Lazarus Group, Jade Sleet and APT38. Binance says the tactics mirror the Contagious Interview and Operation Dream Job campaigns.
How did a fake job interview lead to the Binance heist?
A fake Project Director contacted a Binance engineer on a job platform and ran two interviews. The engineer then downloaded a coding assignment that installed custom malware. Attackers used that computer to reach more engineers and a deployment token.
How much money did Binance recover?
As of November 3, 2026, about $2.85 billion in stolen assets was frozen or intercepted. Binance also says it replaced 98 percent of the impacted token assets by October 31.
How can companies stop fake job interview attacks?
Ban take home coding tasks on work computers, use separate devices for interviews, keep deployment tokens off laptops, limit what internal AI tools can reach, and watch for permission changes as closely as transfers.
What is EIP-7702 and why did it matter?
EIP-7702 is an Ethereum feature that lets a wallet delegate control to contract code. Attackers abused it to keep stealing after Binance suspended withdrawals.

