Malicious code in jest-canvas-mock (npm)
The npm account `atool` was compromised and used to publish 631 malicious versions across 314 npm packages, including jest-canvas-mock, in an automated 22-minute burst. Each malicious version injects a preinstall hook executing an obfuscated Bun script that exfiltrates credentials and establishes persistence via CI/CD workflow injection and system daemons.
- Disclosed
- Last updated
- Blast radius
- 631 malicious versions across 314 npm packages; widespread exposure to any project installing affected versions
- Attack vectors
- Threat actor
- Affected entities
- jest-canvas-mocknpm package compromised with malicious preinstall hook
As part of the "Mini Shai-Hulud" supply chain attack campaign, a threat actor compromised the npm account atool and published 631 malicious versions across 314 npm packages in a rapid 22-minute burst. The jest-canvas-mock package was among those affected, modified to include a malicious preinstall hook.
Each malicious version executes a 498KB obfuscated Bun script during installation, using the GitHub API as a covert exfiltration channel. The script steals a broad range of credentials including AWS keys, GitHub PATs, npm tokens, GCP service accounts, Azure credentials, Kubernetes service account tokens, SSH keys, Docker auth configs, database connection strings, Stripe keys, and Slack tokens.
Beyond credential theft, the attack establishes multiple persistence mechanisms: CI/CD workflow injection via a GitHub Actions workflow named "Run Copilot" that dumps all secrets, AI agent session hooks, and a system daemon named "kitty-monitor". Stolen credentials are committed to attacker-controlled repositories following Dune-themed naming patterns (e.g., harkonnen-melange-742).
The compromise was identified by multiple security sources including Amazon Inspector and Google Open Source Security, confirming the malicious code presence in jest-canvas-mock and linking it to the ongoing "Mini Shai-Hulud is back" worm attributed to the TeamPCP threat actor.
Indicators of compromise
- Packages
- jest-canvas-mock
Remediation
- Immediately audit and revoke all credentials (AWS keys, GitHub PATs, npm tokens, GCP service accounts, Azure credentials, Kubernetes tokens, SSH keys, Docker auth configs, database credentials, Stripe keys, Slack tokens) that may have been exposed on systems that installed affected versions
- Remove or downgrade jest-canvas-mock and all 314 affected npm packages to versions published before the attack window
- Scan CI/CD systems for the 'Run Copilot' GitHub Actions workflow and remove any injected workflows
- Search for and remove the 'kitty-monitor' system daemon from affected systems
- Review git commit history for unexpected commits to attacker-controlled repositories with Dune-themed names
- Implement npm package signature verification and consider using npm audit to identify installed malicious versions
- Monitor for unauthorized access to exfiltrated credentials and enable enhanced logging on all credential-dependent services
Sources
- GitHub Advisory GHSA-55pq-j8p6-fr2h · GitHub Advisory Database
Cite this entry
"Malicious code in jest-canvas-mock (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 27, 2026; last updated July 27, 2026. https://supplychainattack.org/incident/malicious-code-in-jest-canvas-mock-npm-u0e9va
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in @antv/gi-assets-basic (npm)
A threat actor compromised the npm account 'atool' and published 631 malicious versions across 314 npm packages, including @antv/gi-assets-basic, in an automated 22-minute burst. Each malicious version injects a preinstall hook executing an obfuscated Bun script that exfiltrates credentials and establishes persistence via CI/CD workflow injection and system daemons.
Mini Shai HuludnpmOtherAccount takeoverCompromised packageMalicious commit - containedcritical
Malicious code in ai-figure (npm)
The npm account `atool` was compromised and used to publish 631 malicious versions across 314 npm packages, including ai-figure, in an automated attack. Each version injects a preinstall hook executing an obfuscated Bun script that exfiltrates credentials and establishes persistence via CI/CD workflow injection and system daemons.
Mini Shai HuludTeamPCPnpmOtherAccount takeoverCompromised packageMalicious commit - containedcritical
Malicious code in @antv/gi-assets-algorithm (npm)
The npm account `atool` was compromised and used to publish 631 malicious versions across 314 npm packages, including @antv/gi-assets-algorithm, in an automated 22-minute attack. Each malicious version injects a preinstall hook executing an obfuscated Bun script that exfiltrates credentials and establishes persistence via CI/CD workflow injection and system daemons.
Mini Shai HuludnpmOtherAccount takeoverCompromised packageMalicious commit - containedcritical
Malicious code in @antv/gatsby-theme (npm)
The npm account `atool` was compromised and used to publish 631 malicious versions across 314 packages, including @antv/gatsby-theme. Each version injects a preinstall hook executing an obfuscated Bun script that exfiltrates credentials and establishes persistence via CI/CD workflow injection and system daemons.
Mini Shai HuludnpmOtherAccount takeoverCompromised packageMalicious commit