Shai-Hulud npm Supply-Chain Attack: Response and Prevention Guide

Reviewed August 15, 2026. Shai-Hulud was a self-replicating npm supply-chain compromise that stole developer and cloud credentials, published exposed secrets, and used compromised maintainer access to spread into additional packages. CISA’s September 2025 bulletin reported more than 500 affected packages. That number describes the incident at that time; it is not a current allowlist or blocklist.

If your organization installed JavaScript dependencies during the exposure window, treat the issue as a possible credential and build-system compromise—not merely a bad package to remove.

What happened

CISA reported that the malware searched development environments for sensitive credentials, including GitHub personal access tokens and AWS, Google Cloud, and Microsoft Azure API keys. It exfiltrated credentials, uploaded some to public repositories named Shai-Hulud, authenticated to npm as compromised developers, modified other packages, and published compromised versions.

This attack path joins package integrity, developer identity, source control, continuous integration, artifact repositories, and cloud access. A clean workstation scan alone cannot establish that every downstream system is safe.

Immediate response

1. Preserve evidence. Save lockfiles, build logs, package-manager caches, endpoint telemetry, CI logs, and cloud audit events before cleanup.
2. Identify resolved versions. Search package-lock.json, yarn.lock, pnpm-lock.yaml, software bills of materials, container layers, and internal artifact repositories.
3. Contain affected systems. Isolate suspicious developer endpoints and CI runners. Pause releases from pipelines whose credentials or dependencies may be affected.
4. Rotate credentials. Prioritize npm tokens, GitHub PATs, SSH keys, cloud credentials, CI secrets, signing keys, and third-party API keys reachable from the affected environment.
5. Rebuild from known-good inputs. Use reviewed lockfiles and trusted package versions, invalidate tainted caches, and replace immutable artifacts.

Dependency review without false confidence

A top-level dependency list is insufficient because a compromised package can be nested. Use the resolved lockfile and the deployed artifact. Compare package names, versions, integrity hashes, install times, and provenance with authoritative incident intelligence and registry metadata.

npm ls --all
npm audit --omit=dev
npm ci --ignore-scripts

npm audit is one input, not a complete Shai-Hulud detector. Running npm ci --ignore-scripts can reduce install-script execution during analysis, but it can also break packages that legitimately require scripts. Test in an isolated environment and inspect the dependency tree before restoring normal builds.

Credential and account hardening

• Require phishing-resistant MFA for npm, GitHub, identity providers, and cloud administration.
• Replace broad, long-lived tokens with short-lived workload identities or trusted publishing where supported.
• Restrict CI secrets by repository, environment, branch, and job; prevent pull requests from untrusted forks from receiving secrets.
• Review GitHub Apps, OAuth applications, deploy keys, webhooks, branch protection, and secret-scanning alerts.
• Alert on new package publications, new tokens, unusual registry access, public-repository creation, and unexpected cloud API use.

Prevent recurrence

Pin dependencies with reviewed lockfiles, generate an SBOM for shipped artifacts, quarantine new package versions before organization-wide use, and retain a clean internal artifact history. Separate development, build, signing, and production credentials. Require peer review for dependency changes and make provenance and integrity checks part of the release gate.

Incident closure requires evidence: affected assets identified, credentials invalidated, clean artifacts deployed, persistence checks completed, monitoring in place, and owners assigned for remaining risk. ITECS supports these controls through its cybersecurity services.

Primary sources

• CISA: Widespread Supply Chain Compromise Impacting npm Ecosystem
• GitHub: Plan for a more secure npm supply chain
• npm documentation: trusted publishing