Security

Axios npm Supply Chain Compromise: Mitigation Guide

2 min read

Summary

Microsoft warned that malicious Axios npm versions 1.14.1 and 0.30.4 were used in a supply chain attack attributed to Sapphire Sleet. Organizations using the affected packages should immediately rotate secrets, downgrade to safe versions, and review developer endpoints and CI/CD systems for compromise.

Need help with Security?Talk to an Expert

Introduction

Microsoft has disclosed a serious npm supply chain compromise affecting Axios, one of the most widely used JavaScript HTTP libraries. Because Axios is commonly installed on developer workstations and CI/CD pipelines, this incident has broad implications for software supply chain security across Windows, macOS, and Linux environments.

What happened

Two malicious Axios package versions were published on March 31, 2026:

According to Microsoft Threat Intelligence, these releases added a malicious dependency, [email protected], which executed a post-install script during npm install or package updates. The install hook contacted actor-controlled infrastructure and downloaded a second-stage remote access trojan (RAT).

Microsoft attributes the campaign to Sapphire Sleet, a North Korean state actor.

Key technical details

  • The Axios source code itself was reportedly left unchanged.
  • The malicious behavior was introduced through a dependency insertion technique.
  • Affected environments included developer endpoints and CI/CD systems.
  • Payloads were tailored by operating system:
    • Windows: PowerShell-based RAT with persistence via registry Run key
    • macOS: Native binary dropped into /Library/Caches
    • Linux/other: Platform-specific follow-on payloads
  • The malware communicated with known malicious infrastructure linked to Sapphire Sleet.

Why this matters for IT and security teams

This attack highlights how trusted open-source packages can be weaponized without obvious application changes. Even if applications appear to function normally, the compromise can still occur at install time, allowing attackers to steal secrets, establish persistence, and pivot deeper into enterprise environments.

For administrators, the biggest risks are:

  • Compromised developer credentials and tokens
  • Exposed secrets in build systems
  • Malware execution on CI/CD agents
  • Persistent footholds on managed Windows devices

Organizations that installed the affected Axios versions should act immediately:

  1. Downgrade Axios to safe versions:
    • 1.14.0
    • 0.30.3
  2. Rotate secrets and credentials that may have been exposed.
  3. Disable auto-updates for Axios packages until environments are verified clean.
  4. Inspect developer and build systems for signs of compromise, especially persistence mechanisms and suspicious script execution.
  5. Use Microsoft Defender detections and hunting guidance from Microsoft’s advisory to identify malicious components and affected hosts.

Bottom line

The Axios npm compromise is a reminder that package management and CI/CD pipelines are now primary attack surfaces. Security teams should treat affected installs as potential endpoint and credential compromises, not just a package issue.

Need help with Security?

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

Talk to an Expert

Stay updated on Microsoft technologies

Axiosnpmsupply chain attackSapphire SleetMicrosoft Defender

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.