Fake Coding Test Scam: How to Open a Recruiter’s Repo Without Getting Hacked

By Asad Mahmood — founder of Gaugely; builds the AI interviewer this blog writes aboutLast updated 2026-11-18 · 5 min read

Method: product behavior was checked against the live implementation; market and regulatory claims use the linked sources below. Dates change only after claims are re-verified.

SHARELinkedInX

A fake coding test is a take-home assignment from a fake recruiter, built to run malware on your computer. The trap hides inside the project: an npm package you are told to run, a VS Code task that starts once you trust the folder, or one line pushed off-screen. Open any recruiter’s repo in a throwaway environment first.

What is a fake coding test?

It looks like a normal hiring process. A recruiter messages you on LinkedIn or a freelance site, there may be a short call, and then you get a take-home task: clone this repository, get it running, fix a bug or add a feature. The project is real enough to pass a quick look. Somewhere inside it is code that installs a backdoor the moment you run it.

Microsoft wrote this campaign up in March 2026 under the name Contagious Interview. The fake recruiters mostly pose as cryptocurrency trading firms and AI companies, and the targets are software developers. ESET tracks the same activity as DeceptiveDevelopment, says it has been active since at least November 2023, and links it to North Korea. ESET’s list of lure sites includes LinkedIn, Upwork, Freelancer.com, We Work Remotely and Crypto Jobs List.

What they want is what sits on a developer’s laptop: crypto wallets, saved browser passwords, password manager data and logins to developer accounts. In its report for April to September 2026, ESET says the group moved from job-interview lures to wider software supply-chain attacks, using stolen developer logins to inject malicious code into source code repositories.

Where the trap hides in the repo

None of these needs you to read the bad code. They only need you to run the project, or to tell your editor you trust it.

  • An npm package you are told to install and run. Microsoft says victims are asked to clone and run an npm package hosted on GitHub, GitLab or Bitbucket, which then loads the malware.
  • A VS Code task file. In recent cases, opening the project asks you to trust the authors; if you say yes, VS Code runs the task in .vscode/tasks.json, which downloads the backdoor (Microsoft).
  • One line pushed off-screen. ESET found the code added as a single line behind a long comment in an ordinary file, often backend code, so it stays out of view unless you scroll right or turn on word wrap.
  • A “quick fix” command. Some fake interview sites show a made-up technical error and ask you to paste a command into your terminal to fix it (Microsoft).

How to open a recruiter’s repo safely: 5 steps

Treat every take-home repository from someone you haven’t met as untrusted until you have checked it. These steps cost a few minutes.

  • Use a throwaway virtual machine or a cloud dev environment, never your main computer. Microsoft recommends a separate environment that is wiped after use.
  • When VS Code asks, choose “No, I don’t trust the authors”. In Restricted Mode, VS Code doesn’t run tasks.
  • Before you run npm install, read the scripts section of package.json and every file in the .vscode folder. Turn on word wrap so a long line can’t hide.
  • Keep SSH keys, crypto wallets, password managers and logged-in browsers out of that environment.
  • Check the company and the recruiter on the company’s own website and careers page, not through links they send you.

Red flags in a coding test

One of these alone can be innocent. Two together are a reason to stop and check.

  • The repository or the recruiter’s account was created very recently.
  • Short links instead of the company’s own domain.
  • Setup steps that are far more complicated than the task.
  • Being asked to trust the authors, turn off antivirus, or paste a command to “fix” an error.
  • Pressure to run it today, before a call with anyone from the team.

What to do if you already ran it

Act as if the computer is compromised. Disconnect it from the internet first.

Then, from a different device you trust, change the passwords you had saved in that browser, revoke and replace SSH keys and access tokens (GitHub, npm, cloud accounts), and move any crypto to a new wallet created on the clean device. Microsoft’s advice is the same: isolate the machine and rotate any credentials it could reach. If it is a work laptop, tell your security team now. Report the fake recruiter to the site where they contacted you.

What a real coding interview looks like

Real companies can test your coding without asking you to run their project on your own computer. Many use a shared editor in the browser. A Gaugely coding interview, for example, runs in a code editor inside the interview page, and the code runs on a server, so there is nothing to clone or install.

A real employer will also answer questions about the role, and the recruiter will be easy to find on the company’s own website.

TL;DR FOR YOUR TEAM

Fake recruiters send developers coding tests that run malware. Where the trap hides, five steps to open a repo safely, and what to do if you ran it.

SHARELinkedInX

Questions people ask

Is it safe to clone a repo from a recruiter?

Cloning and reading the files is usually safe. The risk starts when you install dependencies, run the project, or tell VS Code you trust the folder. Do those steps only in a throwaway environment.

What is Contagious Interview?

Microsoft’s name for a campaign in which fake recruiters send developers coding tests that install malware. ESET tracks the same activity as DeceptiveDevelopment and links it to North Korea.

Does VS Code Restricted Mode stop the attack?

It stops tasks from running, which is one of the methods used. It does not make it safe to run npm install or the project itself on your own machine.

How do I know if a recruiter is fake?

Find the company’s own website and check that the job and the recruiter are listed there. Be wary of brand-new accounts, short links, and pressure to run code before you have spoken to anyone on the team.

SOURCES

KEEP READING