/ The Binance heist, explained

Fake interview repos: what happened at Binance and how to stop them

Binance says the attackers got in through a coding test from a fake recruiter. We walk through the attack step by step and show where Ossprey fits in.

/ How it happened

The interview came after months of groundwork

  1. June 2026

    A tampered install

    A wallet DevOps engineer, searching for an AI coding tool, installed a tampered Homebrew package. Binance caught it, replaced the laptop and rotated credentials. By then the attackers had learned who worked on the wallet team.

  2. September 2026

    The fake interview

    A fake recruiter took a second engineer through two interview rounds, then sent a coding assignment to run on a work laptop. Its setup code swapped the real pyenv tool for a malicious copy, and endpoint tools didn't flag it.

    Run unchecked on a work laptop

  3. 20 October 2026

    Moving sideways

    From that laptop, and using an internal AI tool, the attackers reached the machines of two wallet engineers. One of them held a container deployment token.

  4. 29 October 2026

    The theft

    The attackers used that token to deploy a container and run a script against the wallet signing service. Transfers ran from 20:05 to 23:56 UTC.

/ Where Ossprey fits in

Catch the malicious repo before it reaches a laptop

Ossprey scans a GitHub repo's source and every package it pulls in, then gives you a verdict before anyone clones or runs it.

Scan any repo, including ones you don't own

Paste a GitHub link into Scan Online and get a verdict on the repo and its dependencies.

Watch your organisation's repos

The GitHub App scans every pull request and re-checks dependencies nightly, then alerts or blocks the merge.

Evidence your security team can use

Every finding is graded and comes with a threat report showing what the code does.

Scan Online. Paste a repo, pick the branch and include its dependencies.

Scan your first repo today

Your first scan

01

Create a free account at

02

Open Scan Online, choose GitHub repo and paste the link.

03

Read the verdict, then open the threat report for anything flagged.

Free

For individuals

£0, free forever

For checking a repo before you run it.

  • GitHub repository scanning
  • A daily live scan quota to check repos before opening
Scan your repo free

Pro

For businesses and teams

10-day free trial

For security teams covering many repositories.

Everything in Free, plus:

  • A bigger live scan quota to protect your whole estate
  • Continuous monitoring of your organisation's repos
  • A triage workflow for every finding
  • And much more
Talk to sales

Need unlimited seats, SSO or custom alert rules? Ask about Enterprise

/ In the dashboard

What a repo scan looks like

Ossprey's take on the Binance heistThe engineer's laptop is the new front doorRead our analysis