Malware in node-path-utils
Malware was discovered in the npm package node-path-utils. Systems with this package installed are considered fully compromised and require immediate remediation including secret rotation and package removal.
- Disclosed
- Last updated
- Blast radius
- Any system with node-path-utils installed or running
- Ecosystems
- Attack vectors
- Affected entities
- node-path-utils
A malware incident was identified in the npm package node-path-utils. According to the GitHub Advisory (GHSA-7qr8-pqwp-95p9), any computer with this package installed or running should be considered fully compromised.\n\nThe advisory recommends that all secrets and keys stored on affected computers be rotated immediately from a different, uncompromised system. While the package should be removed, the advisory notes that full control of the computer may have been given to an outside entity, meaning removal of the package alone may not eliminate all malicious software that resulted from the installation.\n\nThis represents a critical supply chain compromise affecting npm users who installed the affected package.
Indicators of compromise
- Packages
- node-path-utils
Remediation
- Immediately rotate all secrets and keys stored on affected computers from a different, uncompromised system
- Remove the node-path-utils package from all affected systems
- Conduct a full security audit of any system that had this package installed
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider the affected system(s) as potentially fully compromised and plan for complete rebuild if critical systems are involved
Sources
- GitHub Advisory GHSA-7qr8-pqwp-95p9 · GitHub Advisory Database
Cite this entry
"Malware in node-path-utils." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 22, 2026; last updated June 22, 2026. https://supplychainattack.org/incident/malware-in-node-path-utils-uspfwy
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 sme-rko-finance-front-operations-feed-models (npm)
The npm package sme-rko-finance-front-operations-feed-models contained malicious code that downloads and executes attacker-controlled native binaries from remote servers upon package load. The malware uses obfuscation techniques including fragmented string arrays, platform-specific endpoints, and DNS TXT record fallbacks to evade detection.
npmCompromised package - resolvedcritical
Malicious code in sme-rko-finance-front-operations-domain (npm)
The npm package sme-rko-finance-front-operations-domain contained malicious code that downloads and executes platform-specific native binaries from attacker-controlled servers. The package uses obfuscation techniques to evade detection and includes DNS-TXT fallback channels to bypass HTTP egress controls.
npmCompromised package - resolvedcritical
Malicious code in sme-rko-finance-front-operations-fee (npm)
The npm package sme-rko-finance-front-operations-fee contained malicious code that executed a binary dropper at require/import time, fetching and executing platform-specific payloads from attacker-controlled Cloudflare Workers and DNS-TXT fallback channels. Installation or import of the package resulted in remote code execution on the host system.
npmCompromised package - resolvedcritical
Malicious code in localization-fixer (npm)
The npm package localization-fixer contained malicious code that fetches and executes arbitrary JavaScript from attacker-controlled jsonbin.io endpoints on package require, granting full Node.js capabilities to remote payloads.
npmCompromised package