Week 45: A fake job interview led to the $6.3B Binance hack. Inspect take-home tests first
Binance says its $6.3B theft started with a booby-trapped coding test. How to inspect a take-home repo safely: scripts, editor tasks, hidden code, a sandbox.
October 28 to November 3. The biggest theft in crypto history started the way a lot of developer compromises start: with a recruiter message and a coding exercise.
What happened
On November 3 Binance published a preliminary account of the theft of about $6.34 billion. It says North Korea-linked hackers began with a fake job interview aimed at one of its engineers, and a tampered file on a work laptop gave them a route into the exchange’s wallet systems (BleepingComputer, Axios).
The timeline, as reported:
- June: a wallet-team employee downloaded a tampered internet tool through a malicious ad. Binance replaced the device and changed credentials, but the attackers had already learned about the employee and the team (Korea Times, BeInCrypto).
- September: a fake recruiter reached another engineer through a legitimate job site. Two rounds of interviews ended with a coding exercise that hid malware (Tech Insider).
- October 29: the money left the exchange, drained through a third engineer’s computer (Korea Times).
The FBI attributed it to TraderTraitor, a North Korean group linked to Lazarus. North Korea denies it (PBX Science). Binance says it froze about $2.85 billion, and that it detected and stopped 57 other suspected North Korea-linked attempts this year, including more fake interviews and poisoned packages (Cybernews).
None of this is new. The campaigns are known as Contagious Interview and Operation Dream Job, and smaller versions of them hit developers every week. What changed is the size of the bill.
So here’s the routine for any take-home test, from any company. It takes about ten minutes.
Walkthrough: inspect a take-home repo before it runs
The rule underneath all of this: cloning a repo is safe. Installing, building, testing or opening it in an editor that trusts the folder is running it. So you read first, then run it somewhere that has nothing to steal.
1. Clone it, don’t open it. Plain git clone doesn’t execute anything from the repo. Don’t double-click it into VS Code yet.
git clone https://github.com/some-company/take-home.git
cd take-home
2. Check for code that runs when the folder opens. VS Code tasks can be set to start automatically when a folder opens. That’s a known trick in these campaigns.
ls -la .vscode .idea 2>/dev/null
grep -rn '"runOn"' .vscode/ 2>/dev/null
A task with "runOn": "folderOpen" in a take-home test is a red flag. If you do open the folder in VS Code, choose Don’t Trust at the Workspace Trust prompt. Restricted Mode blocks tasks and most extensions.
3. Check what runs on install. npm runs preinstall, install, postinstall and prepare scripts automatically.
jq '.scripts' package.json
Read every script. Anything that runs node something.js you haven’t looked at, downloads a file, or runs a long encoded string gets read in full before you go any further. For Python, read setup.py and the build section of pyproject.toml the same way.
4. Look for code hidden off the edge of the screen. A common trick is to pad a line with spaces so the payload sits far past where your editor stops showing it. Very long lines in source files are worth a look:
git ls-files -z | xargs -0 awk 'length > 300 { print FILENAME ":" FNR ": " length " chars" }' 2>/dev/null
Minified vendor files will show up here and that’s normal. A 4,000-character line in tailwind.config.js is not.
5. Grep for the usual suspects. Dynamic execution, child processes and encoded blobs:
grep -rnE "eval\(|new Function|child_process|execSync|spawn\(|atob\(|fromCharCode|base64" \
--include='*.js' --include='*.mjs' --include='*.cjs' --include='*.ts' --include='*.py' . \
| grep -v node_modules
A take-home React app has no reason to spawn a shell or decode base64 at startup.
6. Look at the dependencies you don’t recognize. A brand-new package with one maintainer and a name one letter off from a popular one is exactly what this looks like.
jq -r '(.dependencies // {}) + (.devDependencies // {}) | keys[]' package.json
npm view some-unfamiliar-package time.created maintainers repository.url
7. Run it somewhere with nothing to steal. Not your laptop, and never a work laptop. A throwaway VM is best. A container is a decent second choice if you mount only the project folder and nothing else: no home directory, no SSH keys, no cloud credentials.
Install with scripts turned off, then run with the network cut:
docker run --rm -it -v "$PWD":/app -w /app node:22 npm ci --ignore-scripts
docker run --rm -it --network none -v "$PWD":/app -w /app node:22 npm test
If the task genuinely won’t work without its install scripts or the network, that’s a question for the recruiter, and a fair one to ask out loud.
8. Notice the process, not just the code. Pressure to run the project before any real technical conversation, being asked to install a specific video-call app, and a “fix this bug in our product” task built on a private repo are all worth a second look. A legitimate employer won’t mind if you ask to do the exercise in your own sandbox.
If you already ran it
Treat the machine as compromised. From a different, clean device, change your passwords and revoke sessions and tokens: GitHub, cloud consoles, your password manager, anything crypto. Then check the machine for persistence before you decide whether to wipe it (you probably should):
# macOS
ls -la ~/Library/LaunchAgents /Library/LaunchAgents /Library/LaunchDaemons
# Linux
crontab -l; ls ~/.config/autostart 2>/dev/null; systemctl --user list-unit-files --state=enabled
cat ~/.ssh/authorized_keys
On Windows, check scheduled tasks and Run keys:
Get-ScheduledTask | Where-Object { $_.TaskPath -notlike '\Microsoft*' }
Get-ItemProperty HKCU:\Software\Microsoft\Windows\CurrentVersion\Run
If it was a work laptop, tell your security team today. Binance’s story shows how far one laptop can go.
New write-ups and both weekly posts land in the inbox — subscribe, or grab the RSS feed.