Malware in test-pkg-pnpm
Malware was discovered in the npm package test-pkg-pnpm. The package grants full system compromise to attackers and should be considered a critical threat to any system where it was installed or executed.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed
- Ecosystems
- Attack vectors
- Affected entities
- test-pkg-pnpm
A malicious npm package named test-pkg-pnpm was identified and published to the npm registry. The package contains malware that provides complete system compromise to an attacker.\n\nAny computer with this package installed or running should be considered fully compromised. All secrets, keys, and credentials stored on affected systems should be rotated immediately from a different, unaffected computer.\n\nWhile the package should be removed, complete remediation cannot be guaranteed due to the potential for the malware to have established persistent access or additional backdoors on the compromised system.\n\nThe incident was disclosed via GitHub Advisory GHSA-7grv-5j2w-4wx3.
Indicators of compromise
- Packages
- test-pkg-pnpm
Remediation
- Immediately remove the test-pkg-pnpm package from all systems
- Rotate all secrets, API keys, and credentials from a clean, unaffected computer
- Perform a full security audit and malware scan of any system that had the package installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider the affected system(s) compromised and plan for full rebuild if critical infrastructure
- Monitor for any persistence mechanisms or additional malware that may have been installed
Sources
- GitHub Advisory GHSA-7grv-5j2w-4wx3 · GitHub Advisory Database
Cite this entry
"Malware in test-pkg-pnpm." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 19, 2026; last updated August 19, 2026. https://supplychainattack.org/incident/malware-in-test-pkg-pnpm-1vrgqn
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- resolvedcritical
Malicious code in rust-testing-utils (npm)
The npm package rust-testing-utils contained malicious code that impersonates the pino logger and executes remotely-fetched code with arbitrary privileges. The package spawns a child process that decodes a hardcoded URL, fetches attacker-controlled content, and executes it via Function constructor with full module-loading capability.
npmCompromised packageMalicious commit - containedcritical
Malicious code in stillm4ddpocs-demo-sprocket (npm)
The npm package stillm4ddpocs-demo-sprocket version 999.9.12 contains malicious code that exfiltrates system and project metadata via multiple channels (HTTPS, HTTP, and DNS) to a hardcoded callback host. The package uses a high version number to exploit dependency-confusion attacks against organizations with internal packages of the same name.
npmCompromised packageDependency confusion - containedcritical
Malicious code in @syncraft-labs/react (npm)
The npm package @syncraft-labs/react contained obfuscated malicious code in its ESM distribution that implements the EtherHiding pattern, fetching and executing arbitrary code from an Ethereum smart contract via RPC endpoints. The tampering occurred post-build in the dist/index.js artifact.
npmCompromised package - containedcritical
Malware in hydration-dim-kit
Malware was discovered in the npm package hydration-dim-kit. Any computer with this package installed or running should be considered fully compromised. All secrets and keys must be rotated immediately from a different computer.
npmCompromised package