Microsoft Threat Intelligence identified a widespread npm supply chain compromise affecting over 400 packages, including those linked to major enterprise ecosystems. The attack uses a Mini Shai-Hulud variant worm delivered via a Bun-based JavaScript payload executed automatically by npm preinstall hooks before package installation completes. The malware collects credentials from local files, environment variables, and command-line tools on developer workstations and CI/CD systems, then authenticates to npm, GitHub, AWS, Kubernetes, and HashiCorp Vault to enumerate and exfiltrate sensitive data. It propagates by obtaining npm publishing tokens, modifying package tarballs to insert malicious code and preinstall hooks, incrementing patch versions, and republishing the packages. Additionally, it injects malicious configuration files into GitHub repositories to establish persistence and enable further infection. The attack chain bypasses conventional security checks by executing early in the package installation process and leverages stolen credentials for lateral movement and propagation.

The attack compromises developer workstations and CI/CD environments by stealing a wide range of credentials, enabling unauthorized access to npm packages, GitHub repositories, cloud infrastructure, and secret stores. This leads to unauthorized package modifications, data exfiltration, and persistent infection across multiple software supply chains. The self-propagating nature of the worm increases the scale and speed of compromise, potentially affecting numerous downstream consumers of the infected packages. The integrity of software supply chains and cloud environments is severely undermined, posing significant risks to organizations relying on affected npm packages.

Organizations that installed affected npm packages with lifecycle scripts enabled should consider the associated developer workstations and build runners as compromised. Immediate actions include revoking and rotating all exposed credentials from a known-clean environment. Investigations should focus on unauthorized npm releases, unexpected repository or workflow changes, suspicious cloud and secret-store access, and artifacts from affected build systems. Affected systems and downstream artifacts should be rebuilt from trusted sources. Follow Microsoft’s detailed detection, protection, and hunting guidance available in their advisory. No official patch exists for the packages themselves since the compromise involves unauthorized republishing; remediation relies on credential management and rebuilding from clean sources.