• Security
  • Story
  • Nov 3, 2026

A fake recruiter's coding test got into Binance: run yours in a VM

My take: A recruiter's coding test is a stranger's code. It belongs in a throwaway virtual machine, never on the laptop that holds your keys.

What to know

  • On November 3, 2026, Binance, a cryptocurrency exchange, published its first findings on the theft it suffered on October 29. The way in was a job offer. In September, a software engineer was contacted on a legitimate job-hunting site by a fake "Project Director". First interview: a video call with a fake HR person, who shared a social media account with personal photos and videos to build trust. Second: the "CEO" of a fictitious company, on a chat app, told him to download a coding assignment onto his work computer.
  • The assignment's setup script swapped pyenv, a Python tool installed with Homebrew, for a malicious copy. Binance says its endpoint security tools did not detect the malware at the time. By October 20, from that laptop and through an internal AI tool, the attackers had compromised two colleagues; on October 29, a deployment token found on one of their computers let them run their own script.
  • On October 31, 2026, the FBI attributed the theft to North Korea, under the name TraderTraitor.

Spotted on @nathanv_info, in French.

What changes

The lesson holds for every developer. A take-home test is code from a stranger, and its install step runs with your rights, next to your SSH keys, your tokens and your company's access. Run it in a throwaway virtual machine (Quickemu makes one in two commands on a Mac or a Linux PC), or on a spare computer that holds none of your accounts, then delete it. Read the install scripts before you run them. And a recruiter who insists the test must run on your usual machine has told you enough.

Source: Binance, “29 October 2026 Binance Security Incident: Initial Findings and Response Update”, November 3, 2026

Drafted with Claude, Anthropic's AI, from my take. Reviewed and owned by me.

Up next