Description

The job search process has become a new attack surface for software engineers, as Microsoft Defender Experts uncovered a coordinated campaign leveraging malicious repositories disguised as legitimate Next.js projects and coding assessment materials. Threat actors exploit the pressure and urgency surrounding technical interviews, tricking developers into cloning and executing compromised repositories. These repositories appear authentic but contain hidden malicious logic designed to execute during routine development activities. Telemetry suggests this activity is part of a broader cluster of job-themed lures crafted to blend seamlessly into everyday developer workflows, increasing the likelihood that targets will unknowingly execute attacker-controlled code. The attackers weaponize common development tools and automation mechanisms. Three primary execution paths were identified. First, Visual Studio Code workspace automation is abused through malicious .vscode/tasks.json files configured to execute upon “folderOpen,” triggering code as soon as the project is opened and trusted. Second, build-time execution occurs when developers run commands such as npm run dev, where trojanized JavaScript libraries (e.g., modified jquery.min.js) silently execute malicious payloads. Third, server startup triggers backend-based exfiltration, where sensitive environment variables (process.env) are transmitted to attacker-controlled infrastructure before remote code execution begins. These entry points ultimately converge into staged command-and-control activity. The attack progresses in two stages: an initial lightweight registrar that fingerprints the host and establishes persistent identity with attacker infrastructure, followed by an in-memory tasking client that enables directory browsing, file staging, and data exfiltration. Developers are specifically targeted because their systems often contain high-value assets such as source code, API keys, cloud credentials, and build pipeline access. When executed on corporate devices, the compromise can extend beyond individual endpoints into enterprise environments. Organizations should treat developer workflows as critical attack surfaces and monitor unusual Node.js execution, outbound connections, and suspicious file upload activity from development systems.