Security
Binance's ~$6.3B hack began with a fake job interview (2026-11-04)
Binance’s account of a roughly $6.3 billion theft begins with a recruiting approach. In the explanation covered by the SAZ Labs short, a software engineer was contacted in September by someone posing as a project director. Video interviews followed, giving the interaction the appearance of a hiring process before the engineer was asked to download a coding assignment.
The assignment was downloaded onto a work computer and contained malware, according to the script. That is the turning point in the reported sequence. What appeared to be a task for an interview became a way into the working environment. The source’s practical warning follows directly from that step: do not run code from a stranger on a work machine.
From there, the attackers used an internal AI tool to reach the computers of two wallet engineers. The brief does not explain the tool’s configuration or the exact method used to move between computers. It establishes a reported path from the initial infected machine toward systems used by staff working with wallets, without providing the technical detail needed to reconstruct that path.
Funds began leaving Binance’s hot wallets on October 29. Binance explained the incident on November 3, and the script says the FBI has linked the attack to North Korea. Those are attributed claims in the supplied account. The article does not add an independent attribution or a more detailed description of who carried out the operation.
Binance says about $2.85 billion has been frozen and that users will not be affected. Frozen funds and the overall amount reported stolen are separate figures; the brief does not present the frozen amount as a completed recovery of the entire loss. The central lesson of this short is the route into the organization: an apparently credible interview process led to untrusted code running on a work computer. Keeping that initial step visible makes the story more useful than focusing only on the final dollar amount. The original short below covers the reported sequence and Binance’s response.
Book a call