Security

Malicious Next.js Repos Target Developers via VS Code

3 min read

Summary

Microsoft Defender Experts uncovered a campaign using malicious Next.js repositories, often disguised as job take-home assignments, to compromise developers through normal VS Code and app startup workflows. The repos can automatically execute attacker-controlled JavaScript on folder open or when the project is run, potentially exposing source code, environment variables, and cloud credentials—making this a serious supply-chain and developer workstation security threat.

Need help with Security?Talk to an Expert

Introduction: why this matters

Developer workstations and build environments are high-value targets because they often hold source code, signing material, and secrets (API tokens, cloud credentials) in environment variables. Microsoft Defender Experts reports a campaign seeding malicious Next.js repositories—often wrapped as job-related “take-home” assessments—designed to blend into normal developer workflows and reliably trigger code execution.

What’s new / key findings

Microsoft observed multiple related repositories with shared naming conventions and reused loader logic. While the initial lure varies, the end state is consistent: runtime retrieval and in-memory execution of attacker-controlled JavaScript, followed by staged C2.

1) VS Code workspace execution on folder open

Some repos include .vscode/tasks.json configured with runOn: "folderOpen". If a developer opens (and trusts) the project, a task runs automatically and launches a Node script that fetches a JavaScript loader (observed staged on Vercel) and executes it.

2) Build-time execution when running the app

Other variants trigger when a developer starts the project (for example, npm run dev). These repos embed malicious logic in seemingly normal assets (e.g., a trojanized jquery.min.js). The asset decodes a base64 URL, retrieves the loader (again, frequently from Vercel), and executes it in memory.

3) Backend startup execution with env exfiltration + dynamic RCE

A third path activates during server initialization/module import. Repos may contain a .env value like AUTH_API=<base64>. On startup, backend code decodes the endpoint, posts process.env to the attacker, then executes returned JavaScript using dynamic compilation (e.g., new Function("require", response.data)(require)). This can leak sensitive configuration and enables operator-driven follow-on payload delivery.

Stage 1 registration → staged command-and-control

Across all paths, execution converges on an initial “registrar” stage that profiles the host and polls a registration endpoint, receiving an instanceId to correlate subsequent activity. Telemetry also noted persistent callbacks to attacker-controlled infrastructure (including HTTP traffic on port 300) after initial staging.

Impact for IT admins and security teams

  • Higher risk on developer endpoints: Opening a repo can be enough to execute code if workspace tasks are trusted.
  • Credential exposure: The backend startup path can exfiltrate environment variables (cloud keys, database credentials, CI tokens).
  • Harder detection: In-memory execution and staged loaders can reduce obvious on-disk artifacts.

Action items / next steps

  • Developer guidance: Treat take-home assessments and unfamiliar repos as untrusted; avoid clicking “Trust” in VS Code until reviewed.
  • Repo inspection: Flag/inspect .vscode/tasks.json (especially runOn: "folderOpen"), unexpected Node scripts under .vscode/, and minified libraries that don’t match known-good hashes.
  • Secret hygiene: Reduce reliance on long-lived secrets in .env; use managed identities/short-lived tokens where possible and rotate any exposed credentials.
  • Detection & controls: Monitor Node.js processes for unusual outbound connections (e.g., dev tools calling staging domains followed by unknown C2), and consider egress restrictions from developer devices and build agents.
  • Hunting: Search code hosting and internal mirrors for naming “families” and structural reuse patterns described by Microsoft (near-duplicate repos, similar loaders, repeated staging endpoints).

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

Microsoft DefenderNext.jssupply chain securityVisual Studio CodeNode.js

Related Posts

Security

Microsoft Sentinel Named a 2026 SIEM Leader

Microsoft has been named a Leader in the 2026 Gartner Magic Quadrant for SIEM, highlighting the continued momentum behind Microsoft Sentinel. The announcement also underscores Microsoft's push toward integrated, AI-powered security operations through deep Sentinel integration with the new Integrated Security Operations Center in Microsoft Defender.

Security

Microsoft Perception GA: Agentic Security at Ignite

Microsoft has made Microsoft Perception generally available, introducing an agentic security platform that coordinates red, blue, and green team agents through automated playbooks. Announced at Ignite 2026, the update also expands Defender and Sentinel capabilities to help security teams detect, investigate, and remediate AI-speed threats while keeping administrators in control.

Security

Device Code Phishing Risks for AI Coding Agents

Microsoft warns that device code phishing can be used against AI coding agents such as GitHub Copilot CLI, not just user mailboxes or cloud apps. In a controlled lab, a single approved device code sign-in could enable remote session steering, memory poisoning, synced session exposure, and private repository access depending on account permissions and enabled features.

Security

Microsoft 365 Outage Phishing Campaign Targets Users

Microsoft Threat Intelligence reported a high-volume phishing campaign that impersonates Microsoft 365 service-health notifications to trick users into clicking malicious links. The campaign matters because it uses outage-themed urgency and recipient-specific tracking to target multiple industries, increasing the risk of credential theft and follow-on account compromise.

Security

SCKit ScreenConnect Attack: MSPs Must Hunt Now

Microsoft Threat Intelligence confirmed a campaign abusing ConnectWise ScreenConnect to deploy unauthorized remote-access clients and the SCKit worm on MSP-managed endpoints. The activity can also target technician sessions, making this a high-priority incident for defenders because removing a rogue client alone does not eliminate persistence or invalidate exposed sessions.

Security

AI Agent Supply Chain Attacks Target Coding Tools

Microsoft Security researchers detailed two post-training supply chain attack paths that can backdoor coding and terminal agents: dataset poisoning and model poisoning. The findings matter because compromised agents can misuse tools, execute commands, and access sensitive environments even when prompts appear benign, reinforcing the need for stronger controls around training data, model provenance, and tool permissions.