Malware in pathfix
The npm package pathfix contains malware that grants full system compromise to attackers. Any computer with this package installed or running should be considered fully compromised and all secrets and keys rotated immediately from a different machine.
- Disclosed
- Last updated
- Blast radius
- Any system with pathfix installed or running
- Ecosystems
- Attack vectors
- Affected entities
- pathfix
The npm package pathfix has been identified as containing malware. According to the GitHub Advisory (GHSA-623x-x2wh-q9xq), any computer that has 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 computer. While the package should be removed, there is no guarantee that removal will eliminate all malicious software that may have been installed as a result of the initial compromise, given that the attacker may have gained full control of the system.\n\nAffected users should treat their systems as potentially fully compromised and take appropriate incident response measures.
Indicators of compromise
- Packages
- pathfix
Remediation
- Immediately isolate any computer with pathfix installed from the network
- Rotate all secrets, API keys, credentials, and signing keys from a different, uncompromised computer
- Remove the pathfix package from all systems
- Conduct a full forensic investigation of affected systems to identify any additional malicious software or persistence mechanisms
- Monitor for unauthorized access or activity on accounts that may have been compromised
- Consider full system reimaging if full compromise is suspected
Sources
- GitHub Advisory GHSA-623x-x2wh-q9xq · GitHub Advisory Database
Cite this entry
"Malware in pathfix." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 25, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-pathfix-eakbcu
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 test2221 (npm)
The npm package test2221 version 2.2.4 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
npmCompromised package - containedcritical
Malware in n8n-nodes-trust-me-im-totally-safe
Malware was discovered in the npm package n8n-nodes-trust-me-im-totally-safe, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
npmCompromised package - activecritical
Malware in litespeed-cache
Malware discovered in the npm package litespeed-cache. The package grants full system compromise to attackers, requiring immediate removal and credential rotation from a clean system.
npmCompromised package - containedcritical
Malware in open-worker-cli
Malware was discovered in the npm package open-worker-cli. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
npmCompromised package