Skip to content
supplychainattack.orgSupply chain attack incident catalog
resolvedcritical

Behind the Scenes: How StepSecurity Detected and Helped Remediate the Largest npm Supply Chain Attack

StepSecurity detected a compromise of axios, described as the largest npm supply chain attack on a single package by download count. A state-sponsored threat actor is reported to have actively suppressed warnings by deleting GitHub issues. Detection occurred before public disclosure.

ShareXLinkedInHacker News
Disclosed
Last updated
Blast radius
Very large - axios is one of the most widely downloaded npm packages; direct impact on all downstream dependents.
Ecosystems
Attack vectors
Threat actor
Affected entities
  • axios

StepSecurity's AI Package Analyst and Harden-Runner tools detected the compromise of axios, one of the most widely-downloaded npm packages, prior to any public disclosure. Axios is an HTTP client library with massive adoption across the JavaScript ecosystem, making this incident significant in scope.

The response involved a coordinated effort to disclose and remediate the compromise. A community call was organized at midnight that drew approximately 200 attendees. StepSecurity identified indicators of state-sponsored activity, including deliberate deletion of GitHub issues to suppress early warnings of the compromise.

The incident received significant media coverage, including reports from Bloomberg and commentary from notable figures in the AI/ML community. The exact nature of the malicious payload and affected versions are not detailed in this summary source material.

Indicators of compromise

Packages
  • axios

Remediation

  • Update axios to a patched version released after the compromise was disclosed
  • Review audit logs for axios dependency installations during the incident window
  • Scan downstream projects for any artifacts or behavior introduced by compromised axios versions
  • Monitor for follow-on exploitation or lateral movement from systems that may have executed compromised code
  • Enable strict package verification and signing requirements in dependency management workflows

Sources

  1. Behind the Scenes: How StepSecurity Detected and Helped Remediate the Largest npm Supply Chain Attack · StepSecurity

Cite this entry

"Behind the Scenes: How StepSecurity Detected and Helped Remediate the Largest npm Supply Chain Attack." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed April 9, 2026; last updated June 7, 2026. https://supplychainattack.org/incident/behind-the-scenes-how-stepsecurity-detected-and-helped-remediate-the-largest-npm-1fmmcy

Suggest a correction

Found an error or have a newer source? Corrections to factual errors take priority over new entries.

  1. containedhigh

    Microsoft links Mastra AI supply chain attack to North Korean hackers

    Microsoft attributed a Mastra AI supply chain attack that compromised over 140 npm packages to North Korean hacking group Sapphire Sleet (BlueNoroff). The attack targeted the npm ecosystem and AI development infrastructure.

    UNC1069npmAI agents & skillsCompromised packageMalicious maintainer
  2. activecritical

    Mastra npm Supply Chain Attack: 140+ Packages Backdoored via easy-day-js Typosquat

    On June 17, 2026, an attacker compromised the @mastra npm organization and injected easy-day-js, a typosquat of the popular dayjs library, as a dependency across 140+ packages. The malicious package contained an obfuscated postinstall dropper that downloaded and executed a second-stage payload from attacker-controlled servers before self-deleting. The affected packages had a combined weekly download count exceeding 1.1 million.

    npmCompromised packageTyposquattingMalicious maintainer
  3. activecritical

    The Worm That Keeps on Digging: TeamPCP Hits @antv in Latest Wave

    TeamPCP conducted a multi-ecosystem supply chain compromise targeting the @antv package and associated development infrastructure. The attack leveraged GitHub, NPM, and VSCode to steal credentials and establish persistence mechanisms.

    TeamPCPnpmOtherAccount takeoverCompromised packageMalicious maintainer
  4. containedcritical

    Malicious code in intercom-php (Packagist)

    The intercom-php package on Packagist was compromised with malicious code as part of the Mini Shai-Hulud campaign by the TeamPCP threat actor. The malicious payload steals credentials and can propagate to NPM packages using discovered credentials.

    Mini Shai HuludTeamPCPNuGetCompromised packageMalicious maintainer