The Library

Binance Hack: A Fake Job Interview and a Tampered Download Led to the $6.34 Billion Theft, What Is Confirmed and What Businesses Should Check

Binance says a fake job interview and a tampered Homebrew download gave attackers the foothold for a $6.34 billion crypto theft. Here is what is confirmed and what to check on your own team's devices.

Elite Performance Exclusive LLC 6 min read

Where Worldwide

Binance Hack: A Fake Job Interview and a Tampered Download Led to the $6.34 Billion Theft, What Is Confirmed and What Businesses Should Check
On this page 6 sections

The crypto exchange Binance says attackers stole about $6.34 billion in digital assets on October 29, 2026, after getting malware onto employees' work computers through a fake job interview and a tampered software download. If your staff install developer tools from search results or take "coding tests" on work laptops, your company has the same opening.

The FBI attributed the theft to North Korea on October 31, and Binance explained how it happened in a report updated November 3. Below: what is confirmed, what is not, and what to check this week.

How the Binance hack happened

Binance's report describes an attack that was in motion from at least June and went through three employees, called Engineers A, B and C.

When (2026) What Binance says happened
June Engineer A, on the wallet DevOps team, searched for a popular AI coding tool and installed a tampered Homebrew download. Binance replaced the device and rotated credentials, but the wider team was still exposed.
September A fake "Project Director" approached Engineer B on a job-hunting platform. After a video interview with a fake HR person and a chat-app interview with a fake CEO, the engineer downloaded an "assignment" repository to a work computer. Its setup ran malware that got past endpoint protection.
October 20 Using Engineer B's computer and an internal AI tool, the attacker gained control over Engineers A and C. Engineer A's computer held a container deployment token.
October 29 From 17:15 to 19:56 UTC the attacker used Engineer C's computer and Engineer A's credentials to deploy a container and run a script that sent transactions through an internal signing service, outside the normal withdrawal process. The last unauthorized transfer finalized at 23:56 UTC.

Binance says the interview malware replaced part of pyenv, a common Python developer tool, with a malicious copy that took commands from an attacker's server. The attacker also abused EIP-7702, an Ethereum feature that lets an account hand some rights to a smart contract. In 50 transactions the attacker set up malicious delegations on a hot wallet. Those delegations were recorded on the blockchain, so suspending withdrawals did not cancel them. Binance cleared the delegation at 00:10 UTC on October 30.

What is confirmed and what is not

From Binance's report:

  • About $6.34 billion in digital assets were affected.
  • About $2.85 billion has been frozen or intercepted, subject to reconciliation and price changes.
  • As of October 31, 98% of affected token assets had been replenished, and Binance says it will cover the financial impact for users.
  • Binance rebuilt the wallet system in a new environment, rebuilt the internal AI tool and its access controls, replaced devices, retired affected credentials and tokens, and scanned all employee devices.

From the FBI: An FBI alert dated October 31, 2026 says North Korea was responsible for the theft of "more than $6 billion USD in virtual assets" from Binance on or about October 29, and calls the activity TraderTraitor. Together with the Secret Service and IRS Criminal Investigation, the FBI asked exchanges and other services to block transactions tied to the laundering addresses it listed.

Not known: Binance has not named the job platform, the chat app, the AI coding tool or the internal AI tool, and says some technical details will stay confidential. It has not explained exactly how the AI tool was used to reach colleagues. An independent review is underway, so details may change.

Why a fake job interview works on a company network

The fake interview targeted a person, not Binance's systems. The "recruiter" built trust over a video call and a social media account, and the last step looked like a normal hiring task: download a repository and run setup. Developers do that every day. The mistake was doing it on a work computer that could reach company systems.

The June download teaches the same lesson in a different way. Our post on ArmorSteal malware covered fake download sites for Windows tools. Binance's report shows the same trick working against Homebrew on a Mac.

After that, the attacker spread to other machines. One laptop, plus an internal AI tool, gave the attacker access to two more people, and one of them had a deployment token saved on the machine. That token opened the signing service. As our infostealer post showed, attackers use stolen credentials quickly.

A company does not need billions in crypto to be a target. If your staff can deploy code, approve payments or reach customer data, you have something worth stealing this way.

What to do this week

Check How to do it
Keep outside code off work devices Job applications, coding tests and side projects belong on personal devices or a throwaway virtual machine, never a work laptop.
Install tools from official sources Get Homebrew, Python tools and AI coding assistants from the vendor's own site or a managed catalog, not from search ads or look-alike pages.
Find stored tokens Search developer laptops for deployment tokens, cloud keys and SSH keys saved in plain files. Move them to a secrets manager with short expiry.
Require two approvals Require a second person or a hardware key for deployments, payments and production changes, so one laptop is not enough.
Review internal AI tools List what each internal assistant or bot can reach, cut that to the minimum, and log what it does.
Brief staff on recruiter scams The pattern is an unsolicited offer, a friendly video call, then "download this assignment." Ask staff to report it, with no blame.
Rotate credentials team-wide after a warning When one device is flagged, rotate credentials for everyone it touched. Binance's June cleanup left colleagues exposed.

If your team runs its own servers or deployment pipeline, our self-hosting infrastructure page explains how access can be set up so no single device can deploy on its own.

Binance hack questions people are asking

How much was stolen in the Binance hack?

Binance says about $6.34 billion in digital assets were affected on October 29, 2026. The FBI says more than $6 billion.

Who was behind the Binance hack?

The FBI attributes it to North Korea and calls the activity TraderTraitor.

Did Binance customers lose money?

Binance says it will cover the financial impact for users. It also says 98% of affected token assets had been replenished as of October 31.

How did a fake job interview lead to the hack?

An engineer ran a coding "assignment" from a fake employer on a work computer. Its setup script installed malware, which the attacker later used to reach colleagues with access to wallet systems.

How can I spot a fake job interview?

Watch for offers you did not ask for, a company you cannot verify, interviews moved to chat apps, and any request to download and run code. Never run test code on a work device.

The bigger lesson

This $6.34 billion theft did not start with a clever exploit. It started with employees doing ordinary things on work laptops: installing a tool from a search result and taking a coding test. Treat every work device as a key to the company, and make sure no single key opens everything.

Want help locking down developer access and deployments? See security hardening or get a quote.

Get security alerts like this by email, with our free checklist, at security alerts.

Sources: Binance: Initial Findings and Response Update; FBI: North Korea Responsible for $6 Billion+ Binance Attack.

Share X LinkedIn Facebook

Was this article helpful?

We only keep the note with this article. No name, no email.

Protected by reCAPTCHA - Privacy and Terms.

Have a question about this article?

Ask it here and we will answer you directly by email. Questions are private, never posted.

Protected by reCAPTCHA - Privacy and Terms.

Security alerts by email

Hear about the next one first.

When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.

Protected by reCAPTCHA - Privacy and Terms.

Want a result like this?

Security alerts, breaches and the technology a business runs on: what happened, who it affects and what to do.

Get a Tech Quote

Security alerts by email

The next security hole is already out there. Hear about it from us first.

When attackers start using a flaw in software businesses run on, we email what it is, whether it touches you and what to do that week, with a round-up of our latest security writing. Free, one-click unsubscribe. You get the checklist straight away: 12 things to secure this week.

Protected by reCAPTCHA - Privacy and Terms.