The Shai-Hulud npm Worm of August 4, 2026: Full Breakdown of the Attack That Poisoned 1,280+ Packages

On August 4, 2026, the npm ecosystem experienced one of the most devastating software supply chain attacks in history. Attackers compromised the GitHub account of jaredwray — the maintainer of keyv, flat-cache, file-entry-cache, and the cacheable family of caching libraries — and pushed a self-propagating credential-stealing worm. Within hours, the malware, a variant of Mini Shai-Hulud (also called ChainDrop), had spread to over 1,280 packages with a combined ~2 billion monthly downloads . Here is a complete breakdown of what happened, how the attack worked, and the remediation steps recommended by security researchers.

Initial Compromise: How the Attackers Got In

At roughly 09:00 UTC on August 4, 2026, an attacker took control of Jared Wray's GitHub account (jaredwray) . Using that access, they pushed malicious code directly to the main branch of the keyv repository and immediately cut new releases across the entire keyv and cacheable package family .

The initial seed included 11 packages across both namespaces: keyv, cacheable-request, cache-manager, @cacheable/utils, flat-cache, file-entry-cache, and others . Security researchers from Aikido Security, StepSecurity (which tracks the worm as "ChainDrop"), Socket, and Chainguard all independently confirmed the compromise within the first hours .

The Malicious Payload: setup.mjs and Math_Symbol.js

Every poisoned package received the same infection pattern: two new files (setup.mjs and Math_Symbol.js) and a modified package.json with a

"preinstall": "node setup.mjs"

When any developer or CI system ran

npm install

Microsoft Threat Intelligence confirmed that the payload is a Mini Shai-Hulud variant . It harvests a wide range of credentials and secrets from infected environments :

• npm authentication tokens
• GitHub personal access tokens (PATs)
• AWS keys
• Kubernetes secrets
• HashiCorp Vault tokens
• Stripe keys
• Slack tokens
• SSH keys
• Terraform state files
• Docker credentials
• VPN configurations

Self-Propagation: How the Worm Spread Across the Ecosystem

What made this attack particularly dangerous was its ability to self-propagate. After stealing npm publishing tokens and GitHub PATs from the infected environment, the worm used that access to publish additional malicious versions of other packages owned by different, unrelated maintainers .

The scope of the compromise expanded rapidly:

• Within roughly two hours, StepSecurity tracked 435 packages and 1,557 versions poisoned .
• By early afternoon CEST, Aikido Security was counting 868 compromised packages across 1,381 versions .
• By the end of the day, the total exceeded 1,280+ packages and 1,680+ versions, according to BleepingComputer and other outlets .

The worm crossed namespace boundaries — it did not stay within the keyv/cacheable family where it started. It jumped to packages owned by organizations including Deliveroo, Ornikar, OneReach, Picsart, Qlik, and ServiceTitan, among many others .

Exfiltration: Where Stolen Data Went

Stolen credentials were exfiltrated to a GitHub repository controlled by the attacker — the worm either created a new repository or used a dedicated exfiltration repo for this purpose . Multiple redundant exfiltration channels were built into the payload , making it resilient to the takedown of any single channel.

Remediation: What Security Researchers Recommended

Security researchers across multiple firms urged teams to treat any system that touched an affected package as fully compromised. The following remediation steps were consistently recommended :

1. Pin or Roll Back Affected Packages Immediately

Use npm/yarn/pnpm overrides (e.g., "overrides" in package.json) to prevent accidental reinstallation of poisoned versions . Check lockfiles (package-lock.json, yarn.lock, pnpm-lock.yaml) for any affected package versions, including transitive dependencies .

2. Treat Affected Hosts as Fully Compromised

Do not simply delete the malicious files from a machine that ran

npm install

3. Rotate All Credentials

Revoke and regenerate all potentially exposed credentials :

• npm tokens (classic and granular)
• GitHub personal access tokens (PATs) and fine-grained tokens
• AWS IAM keys and access keys
• Kubernetes service account tokens
• HashiCorp Vault tokens
• Stripe keys
• Slack tokens
• SSH keys
• Docker credentials
• VPN tokens

4. Remove Token-Revocation Watchers Before Rotating

A critical detail: the malware sometimes sets up GitHub workflow watchers that can re-expose a new token the moment it is created . Researchers advised disabling or removing any monitoring service before rotating credentials .

5. Clear Caches and Rebuild from Scratch

Clear npm/pnpm/yarn caches and Docker build caches on both developer machines and CI/CD runners . Rebuild all artifacts from scratch to prevent tainted dependencies from persisting in build caches or Docker layers .

6. Audit GitHub and CI/CD Environments

Search for newly created repositories or unauthorized workflows . Look for persistence artifacts such as .claude/settings.json or .vscode/tasks.json that the worm may have created .

Key Takeaways

The Shai-Hulud worm attack of August 4, 2026 was a watershed moment for JavaScript ecosystem security. It demonstrated that a single compromised maintainer account — even without direct access to most of the affected packages — could cascade into a worm that poisoned well over a thousand packages within hours. The attack's use of a legitimate Bun runtime binary for payload execution, its self-propagation via stolen tokens, and its redundant exfiltration channels made it more sophisticated than previous supply chain attacks .

For engineering and security teams, the incident underscores the importance of pinning dependencies, disabling pre/post-install scripts where possible, monitoring for unusual GitHub activity, and maintaining incident response runbooks for supply chain compromises.