Affected Systems

Over 400 npm packages across multiple unrelated publishers, including keyv, flat-cache, cache-manager, and other major enterprise software ecosystem packages. Affects developer workstations and CI/CD environments with npm lifecycle scripts enabled. Targets npm, GitHub, AWS, Kubernetes, and HashiCorp Vault credentials.

Exploitation Status

Active exploitation confirmed. Microsoft Threat Intelligence identified large-scale supply chain attack in progress. Malware (Mini Shai-Hulud variant) actively propagating through npm ecosystem by stealing publishing tokens and automatically republishing compromised packages with incremented patch versions.

Business Impact

Critical supply chain compromise with self-propagating capability. Malware executes automatically via preinstall hooks before security checks run. Steals credentials from developer workstations and CI/CD pipelines, including npm tokens, GitHub access, AWS credentials, Kubernetes secrets, and HashiCorp Vault data. Exfiltrates encrypted data via HTTPS and GitHub repositories. Establishes persistence through Claude and VS Code configuration injection. Organizations with affected packages should assume full compromise of developer systems, build runners, and all accessible credentials.

Urgency

🔴 Immediate

Recommended Actions

  • Audit all npm package installations for unexpected patch version updates with no corresponding source commits or tags; prioritize packages related to keyv, flat-cache, and cache-manager ecosystems
  • Treat any developer workstation or CI/CD runner that installed affected packages with lifecycle scripts enabled as fully compromised; isolate systems immediately
  • Revoke and rotate all npm publishing tokens, GitHub personal access tokens, AWS credentials, Kubernetes secrets, and HashiCorp Vault tokens accessible to affected identities from a known-clean environment
  • Review npm package releases for unauthorized publications, GitHub repositories for injected Claude (.claude) and VS Code (.vscode) configuration files, and cloud audit logs for suspicious AWS, Kubernetes, and Vault access
  • Rebuild affected build systems and re-sign or rebuild all artifacts produced by compromised CI/CD pipelines from trusted sources; disable npm lifecycle scripts (--ignore-scripts flag) until environment is verified clean