All posts

Blog

$6.3 Billion in 20 Minutes: The Binance Hack Started with a Job Offer

November 15, 2026 · SystemDesk team

Hackers took about $6.3 billion from the world’s largest crypto exchange, most of it in around 20 minutes. It began with a fake job interview. Here is the story, the math, and what it means for anyone who controls a computer.

If you have ever answered a message from a recruiter, this story is about you.

On the evening of Thursday, 29 October 2026, someone started emptying the world's biggest crypto exchange. Binance says about $6.3 billion was stolen. The analysts who traced the money say most of it left in roughly 20 minutes, across 10 different blockchains. It is the biggest crypto heist ever recorded.

And the way in was not a genius piece of code. It was a job offer.

The short version: a fake recruiter, a "coding assignment", one infected laptop, and about $6.3 billion gone. Below you will find the numbers, the story step by step, and what you can do about it today.

The numbers that make your stomach drop

$6,300,000,000 / 1,200 seconds = about $5,250,000 every second

By the time you finish reading this sentence, around $20 million would be gone. And that is only the start:

  • 4x the old record. The biggest theft before this one was $1.5 billion, from the exchange Bybit in February 2025. This one is more than four times bigger.
  • 2x a whole year of crypto crime. The analysts at TRM Labs counted $2.87 billion stolen across nearly 150 attacks in all of 2025. This single night was more than double that.
  • 6x the safety net. Binance keeps a $1 billion emergency fund for its users. The theft was more than six times that.
  • 63,000 years of salary. Earn $100,000 a year and you would need about 63,000 years to make $6.3 billion. You would have had to start while Neanderthals were still alive.

How it happened, step by step

Step 1: A message from a "recruiter"

Around September, a Binance software engineer was approached on a legitimate job-hunting platform by someone posing as a project director. Fortune reports that the engineer's profile mentioned his Binance experience. Nothing about it looked unusual. That is the whole point.

Step 2: Two interviews and a fake CEO

A proper hiring process followed. There was a first interview with an "HR representative", then a second with a person claiming to be the CEO of a company that did not exist. Live video, social-media profiles, every trapping of the real thing.

Step 3: The homework

Then came the assignment: a small coding project to download and run.

He ran it on a work computer. Hidden code in the setup quietly swapped a trusted developer tool for a tampered copy and called home to a server the attacker controlled. The security software Binance had at the time did not catch it.

It has happened before. In 2024 the same trick, a fake recruiter and a malicious Python script dressed up as a pre-employment test, was used on an employee of a wallet-software company. The result was the roughly $308 million theft from the Japanese exchange DMM Bitcoin (per the FBI, as cited by StepSecurity).

Step 4: One laptop becomes three (around 20 October)

The attacker used that first computer, together with an internal AI tool, to take control of the computers of two more wallet engineers. One of them had a container-deployment token sitting on it.

You may have read that "AI hacked Binance". It did not. Binance's own account says the attackers relied mainly on old-fashioned phishing. The internal AI tool was a stepping stone from one computer to the next, not the break-in itself.

Step 5: Twenty minutes of noise (29 October)

On the day of the theft, that token was used from the other engineer's machine to launch a container and run a malicious script. The script reached an internal wallet-signing service, which began approving transfers that had nothing to do with the normal withdrawal process.

Weeks of quiet. Twenty minutes of noise.

Why one mistake is enough

Binance says it spotted and stopped 57 hacking attempts that it links to North Korea in 2026. One got through. Now try this with made-up odds:

One employee spots the fake message:         99%
All 100 employees spot it (0.99 ^ 100):      37%
At least one employee falls for it:          63%

Those are invented numbers, not Binance's. The lesson is real, though: attackers only have to win once. Defenders have to win every time.

Who did it, and where did the money go?

The suspects

TRM Labs and Chainalysis point to North Korea's TraderTraitor group, the same unit blamed for the Bybit theft. TRM says it has high confidence. Binance's co-CEO said early on that the investigation had not put the blame on any individual, so treat the name as a strong lead, not a court verdict.

The money

  • If you hold coins on Binance: the company says customer funds are safe and that it, not its users, absorbs the loss. It set aside more than $6.34 billion of its own money and says it had replaced about 98% of the stolen coins by 31 October.
  • What was stopped: roughly $2.5 to $3 billion was frozen or intercepted, including stablecoins frozen by Tether and Circle. Binance's latest figure is about $2.85 billion, still being reconciled.
  • Withdrawals were paused for about 48 hours, then reopened in stages.
  • Still open: the investigation is ongoing and these numbers may change.

One detail that stuck with us. Pausing withdrawals did not cancel the permissions the attacker had already planted on the blockchain. Binance needed a special procedure to revoke them. An emergency brake is only as good as what it can actually undo.

Why a remote desktop company is talking about Binance

Binance is not a company of careless people. It has a security team, and it says it stopped dozens of attacks this year. What failed was something much more ordinary: one computer reached another computer, and every one of them trusted what it could reach.

Here is the lesson in one line: a computer you can reach is a computer someone else might reach. Every extra way into a machine, whether it is a shared token, an internal tool or a remote-access app, is a door. What matters is whether you can see who is using the door, and close it.

That is what we think about all day at SystemDesk, where you control your own computers from anywhere. So here are six questions to ask about any remote-access tool, ours included, and how SystemDesk answers them:

  1. Can you see who is connected right now? The portal shows who is connected to which of your computers at this moment, plus the history of every session.
  2. Can you end it instantly? A live session ends with one click.
  3. Is each computer tied to your account? Every device is linked by a hardware fingerprint. Remove a device and only that device is signed out.
  4. Can you limit what a visitor can do? Permissions are set per device (13 of them, from keyboard and mouse to clipboard, file transfer and terminal), so you allow only what you need.
  5. Is your sign-in protected? Two-factor sign-in with an authenticator app, a lockout after repeated wrong passwords, every sign-in listed, and an audit log you can export.
  6. What does the company keep? Sessions are encrypted end to end between your two devices. We never keep what was on your screen, what you typed, what you copied or the files you moved.

Let us be straight with you. SystemDesk would not have stopped a stranger's "coding assignment" from running on a work laptop, and neither would any other tool. The first click was human. What good tooling does is shrink the blast radius, so one mistake does not become three computers and a very bad Thursday.

Five things to do today

  1. Never run a stranger's "test project" or "assignment" on a computer that holds your real accounts. Use a spare machine or a disposable virtual machine.
  2. Install tools only from the official site. In this story, a different Binance engineer was lured by an online ad to a tampered copy of a popular developer tool.
  3. Do not leave powerful keys, tokens and saved passwords lying around on everyday computers. If the computer falls, everything on it falls too.
  4. Turn on two-factor sign-in on your email, your exchange accounts and your remote-access tools, and prefer an authenticator app.
  5. Check your own doors. Which remote-access tools are installed on your computers? Who is signed in? Which devices are listed? Remove what you do not recognise. Our checklist for any remote desktop tool is a good place to start.

Curious how SystemDesk handles all this? Read how we protect remote sessions, or download SystemDesk free and check the portal for yourself.


Facts checked on 16 November 2026 against reports published between 30 October and 3 November 2026. The investigation is still going, so figures may change. SystemDesk is not connected to Binance. Sources: Fortune, StepSecurity, Cointelegraph and Al Jazeera.