CVCOVANewsComputing, Opportunities, Value & Analysis
Cybersecurity & Privacy4 min read

A fake job interview may have opened the door to the theft of more than $6 billion from Binance: how to avoid the trap

Binance says the theft began with a job offer and a “technical test” containing malicious code. The FBI points to North Korea. Here is how the tactic works and how developers looking for remote work can protect themselves.

By COVA News newsroom
A person in silhouette against multiple computer monitors displaying lines of code

Photo: Kevin Horvat on Unsplash

In September, a Binance engineer received a message on a job platform that looked like a good opportunity. He was contacted by a supposed “Project Director” and then interviewed by someone claiming to be from human resources and by a purported chief executive. After a video call, he was given a technical “assignment.” According to the incident report Binance published on November 3, cited by The Block, The Register, Help Net Security and Axios, that test was the first step in the theft the cryptocurrency platform suffered around October 29. The company and most media outlets put the figure at about $6.3 billion.

The assignment involved downloading a code repository, that is, a folder containing a project’s files, onto the engineer’s work computer. According to Binance, the code concealed “zero-day” malware: a malicious program so new that defenses do not yet recognize it. The company’s security tools did not detect it. According to the same account, on October 20 the attackers used that machine and an internal artificial intelligence tool to take control of two other engineers’ computers.

On the day of the theft, again according to Binance, they deployed a malicious program and abused the service that signs wallet transactions, as well as a technical mechanism called EIP-7702. This allowed them to gain partial control of a “hot wallet,” the kind that stays connected to the internet so funds can be moved quickly. The company also described an earlier episode: in June, an infrastructure engineer installed a tampered version of Homebrew, a widely used tool for installing software, while searching for an AI coding assistant. Binance detected it, but by then the intruders already knew his role and the names of his colleagues.

An accusation with figures that don’t add up

On October 31, the FBI issued an advisory together with the Secret Service and the criminal investigation unit of the IRS, the U.S. tax agency. In it, the FBI attributes the theft to North Korea and the TraderTraitor group, according to NBC and Help Net Security. It is the same group blamed for the theft of about $1.5 billion from Bybit in 2025. Pyongyang rejects the accusation: Kim Yo Jong called it a “political provocation,” according to NBC and Euronews. So far, no independent forensic analysis confirming who was responsible has been made public. Binance itself is cautious, saying that North Korea “appears” to have used the fake interview, according to Axios.

There is no single figure either. TechRadar says the FBI cites more than $6 billion. Help Net Security and NBC mention $6.34 billion, and other outlets go as high as $6.7 billion. Binance says it has frozen or intercepted about $2.85 billion, while Help Net Security puts that figure at close to $3 billion. The company also says it has replenished 98% of the affected assets and, according to Axios, has stopped 57 suspicious incidents linked to North Korea in 2026.

The method is not new. Binance did not formally link the case to any known campaign, although BleepingComputer notes that it resembles “Contagious Interview.” Researchers at Palo Alto Networks’ Unit 42 gave that campaign its name, have tracked it since December 2022 and attribute it with moderate confidence to North Korean actors. The technique typically begins with an NPM package, from the large repository of JavaScript code components, hosted on GitHub. Installing it activates BeaverTail and InvisibleFerret, two programs that steal passwords, payment cards saved in the browser and cryptocurrency wallets. DevOps.com documented variants that are triggered simply by opening the project in the VS Code editor. Silent Push, for its part, found three fake crypto companies set up as fronts.

How to spot a trap interview

For people looking for remote work, the lesson is concrete. Specialists recommend the following:

  • Verify the recruiter and the company through independent channels, for example by checking how long their organization has been on GitHub and what it has published.
  • Be wary of any request to clone, install or run code, even if it sounds routine.
  • Carry out tests only in a disposable virtual machine, a simulated computer running inside your own machine, and never on the computer where you store passwords or keys.
  • Read the automatic scripts in the package.json file and the files in the .vscode folder before running anything, and do not mark a project as “trusted” without reviewing it.

If something suspicious has already been run, the advice is to rotate any access tokens that were used and delete the virtual machine.

Latin American media have covered the case, but there is no data on affected Binance users or funds by country, nor any statements from regulators in the region. Nor are there documented cases of local developers being targeted with this method. The risk, however, knows no borders: any programmer who receives remote job offers could be a target. Still pending are the external investigation Binance has promised and a possible independent confirmation of who was behind the attack.

Sources: Unit 42 (Palo Alto Networks) · Silent Push · MITRE ATT&CK · DevOps.com · Help Net Security

Related news

Cybersecurity & Privacy

An official Microsoft package stole credentials on PyPI: what to check if you use AI agents

Two versions of Microsoft's agent-framework reached PyPI carrying a credential stealer, one day after Google warned of attackers using AI to exploit flaws without human intervention. Here is what development and IT teams in Latin America should check right now.

Cybersecurity & Privacy

Microsoft and FAA outages, FBI and USDA breaches: no evidence of a coordinated attack

Over nine days, service outages and alleged intrusions coincided in the United States, and social media buzzed with talk of a “cyber pandemic.” The evidence points to separate technical failures. The proven danger for users is something else: fake emails that use the outages as bait.

Cybersecurity & Privacy

Nginx: two critical HTTP/2 flaws expose millions of servers; here's how to check and protect yours

F5 has fixed two vulnerabilities in Nginx that allow an attacker to take control of a server without a username or password. Public proof-of-concept code is already circulating. This guide explains how to tell whether your server is at risk, which version to update to and what to do while you wait for your system's patch.