Binance says fake job interview helped enable $6.34B theft
Binance says a fake job interview helped hackers reach wallet systems before a $6.34 billion theft; the FBI attributes the attack to North Korea-linked actors.
The Aeterna Sol Editors

$6.34 billion in digital assets were affected in Binance’s October 29 security incident, according to the exchange’s [initial investigation report](https://www.binance.com/en/square/post/384328127385979). The report says a fake job interview helped attackers compromise an employee’s work computer and reach systems involved in the theft.
Binance describes a campaign that unfolded over several months, combining social engineering, malware, access to an internal AI tool and stolen credentials. The company’s account is preliminary, and it says the investigation is ongoing.
How did a job interview lead to access?
In September, a software engineer whose job-platform profile mentioned Binance was contacted by someone posing as a project director at a fictitious company. The supposed recruiter arranged a video interview with a fake HR representative, then a second interview with someone claiming to be the company’s CEO.
During the second interview, the engineer was asked to download a coding assignment to their work computer. Binance says the repository contained malicious code that ran during setup, using previously undetected malware to compromise the device.
The fake interview was one part of the chain. Binance says an earlier incident in June exposed the roles of employees on its wallet infrastructure team: one had downloaded a tampered version of Homebrew, a software package manager, while installing a developer tool. Binance detected the issue, replaced the device and rotated credentials, but says attackers learned which employees worked on wallet systems.
How did the attackers reach Binance’s wallets?
On October 20, Binance says the attacker used the compromised engineer’s computer and an internal AI tool to gain control of two other engineers’ computers. One had a token that allowed container deployment; a container is a packaged environment used to run software.
On October 29, the attacker accessed another engineer’s computer, used stolen credentials and deployed a container to run a malicious script. Binance says the script let the attacker use an internal wallet signing service to initiate transactions outside the normal withdrawal process.
The exchange reported that five hot wallets—wallets connected to the internet—sent 233.46 million XRP to an attacker-controlled address in four minutes. Other assets were also taken. The FBI says North Korea was responsible and refers to the activity as “TraderTraitor”; it reported that the stolen assets were being converted primarily into ether.
What does Binance say happened to the funds?
Binance says about $2.85 billion had been frozen or intercepted as of its report, subject to reconciliation and market-price changes. It also said 98% of the affected token assets had been replenished as of October 31, with the remaining, less-liquid assets still being purchased.
The exchange says it will absorb the financial impact rather than pass the losses to users. It has rebuilt or replaced systems along the attack path, disabled affected credentials and tokens, and says it is engaging independent security firms to review the incident. Those steps are Binance’s account of its response; the investigation and independent review are not yet complete.
The FBI’s [October 31 alert](https://www.fbi.gov/investigate/cyber/alerts/2026/north-korea-responsible-for-6-billion-binance-attack/layout_view) asks virtual-asset services and other industry operators to block transactions linked to addresses used by the attackers as they launder the stolen assets.