Is a take-home coding challenge safe to run? What to check first

Anand Chapla ·

Treat a take-home coding challenge like any file from a stranger. Check it before you run it, and run it on a computer that holds none of your passwords, keys or accounts. Five checks cover most of the risk: confirm who is asking, use a machine you can throw away, read the project before you run it, open it in a restricted editor mode, and be careful with any rule that stops you from looking closely at the code.

This is not a reason to fear real companies. It is a reason to spend ten minutes before the first command, because in 2026 two separate reports described coding tests that were built to attack the person doing them.

What happened

On 1 September 2026, Kaspersky published a report by Omar Amin about a group it calls Mirage Kitten. It says: “The infection chain begins with fake recruiter accounts contacting prospective targets on a job search platform.” The lure was a coding challenge, a zip file called Front-Technical-Challenge.zip, kept in an Amazon S3 bucket. According to Kaspersky, the README “imposed a three-hour time limit and prohibited the use of AI assistants”. It also claimed that server.js was bug-free and should not be modified.

The first line of server.js imported a package named colorized_terminal, which Kaspersky calls trojanized. The package sat inside the project’s own node_modules folder. When it was imported, it started an implant in the background. Kaspersky adds that an AI code-review assistant “would likely have flagged the suspicious first-line import”.

On 13 November 2026, Dev.ua (Nataliia Khandusenko) reported a second case, this time in a live interview. An engineer, Oleksiy Krychevsky, was told: “Clone the repository, do the task. Google can, AI can’t.” He cloned it into a container and worked in a text editor. The interviewer pushed him: “Dude, open VS Code. Our whole team works in VS Code.” He did not.

According to Dev.ua, the project’s .vscode/settings.json file hid terminal profiles behind a long strip of spaces. Those profiles replaced the terminal’s start command and would have downloaded and run malicious code. The article says the script sends environment variables to the attackers and loads a backdoor that can look for crypto wallets, SSH keys and .env files, read the clipboard and open a remote terminal. Its conclusion: “The attack only failed because the engineer was working in an isolated container via nano and did not open VS Code.”

Two limits on that second story. The engineer’s own write-up, “The Poisoned Interview” (29 October 2026, in Ukrainian), says he studied the files without running the project, so how the code would have started is his reading of the files and not something he watched happen. And we have no way to confirm the other side of it. We use it because the pattern, not the names, is what matters for you.

Five checks before you run anything

These five are our own advice, not a quote from either report.

1. Confirm who is asking. Find the company’s own careers page yourself and check that the role is listed there. Use an email address on the company’s own domain, not the chat message. A real recruiter will not mind that you checked.

2. Use a machine you can throw away. A virtual machine, a container, or an old computer with nothing signed in. The attack in the Dev.ua story looked for wallets, SSH keys and .env files, so the safest computer is one that has none. The engineer who escaped worked in a container.

3. Read before you run. Spend five minutes on the files. Look in hidden folders such as .vscode. Read the scripts section of package.json. Read the first lines of the main file. In the Kaspersky case, the harm was one import on line one, pointing at a package that came bundled with the project. A project that arrives with its dependencies already installed, instead of a list for you to install yourself, is a reason to stop and look.

4. Open an unknown folder in Restricted Mode. VS Code has a feature called Workspace Trust. Its documentation says that when you open a new, unfamiliar folder, VS Code can open it in Restricted Mode “to prevent automatic code execution while you review the contents”. You choose it with the button “No, I don’t trust the authors”. In that mode you can still read and edit the code, but tasks, debugging, some workspace settings and extensions are limited. We have not tested whether it would have stopped the attack in the Dev.ua story, and the page does not list which settings it turns off. It is one layer, not a guarantee, so it goes with check 2, not instead of it.

5. Be careful with rules that stop you from looking. A rule against a tool is not proof of a trap, and many honest companies have one. But when a README says a file is “bug-free” and must not be changed, and says you may not use an assistant, it is worth reading that one file with extra care, by yourself, before you run it. In the Kaspersky case, those two rules pointed the reader away from the one file that held the problem.

If you already ran it

Do these from a different, clean device. Change the passwords for your email and your accounts. Revoke SSH keys, API tokens and any saved logins. If you hold crypto, move it to a new wallet. Treat the first computer as unsafe until it has been wiped. If it was a work laptop, tell your company’s security team the same day, and report the account that sent you the test to the job platform.

If you are the company

Look at this from the other side. A candidate who has read the reports above has good reason to refuse a test that asks them to run unknown code on their own computer, and no good reason to trust one you sent in a chat message. The safest test is one where the candidate’s computer is never part of the risk, and where you tell them in advance exactly what they will see.


Sources: Kaspersky Securelist, “Mirage Kitten: new backdoors NodeRabbit and PollCat” (Omar Amin, 1 September 2026); Dev.ua, Nataliia Khandusenko, 13 November 2026, which also links the engineer’s own write-up, “The Poisoned Interview” (29 October 2026); Visual Studio Code documentation, “Workspace Trust”, read on 17 November 2026. The five checks are our own advice.

codesolara opens every interview in a real VS Code workspace in the browser, with nothing running on the candidate’s machine. Each attempt gets its own container, which is destroyed when the attempt ends (how the sandbox is separated). We build this product, so read the last section with that in mind.

// more