Malware in pump-stream-logger
Malware was discovered in the npm package pump-stream-logger. Systems with this package installed are considered fully compromised and require immediate remediation including credential rotation and package removal.
- Disclosed
- Last updated
- Blast radius
- Any system with pump-stream-logger installed or running
- Ecosystems
- Attack vectors
- Affected entities
- pump-stream-logger
The npm package pump-stream-logger was found to contain malware. According to the GitHub advisory, any computer with this package installed or running should be considered fully compromised.
The 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.
This represents a critical supply chain compromise affecting all users of the pump-stream-logger package.
Indicators of compromise
- Packages
- pump-stream-logger
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the pump-stream-logger package from all affected systems
- Perform a full security audit and malware scan of any system that had pump-stream-logger installed
- Review system logs and access logs for any unauthorized activity during the period the package was installed
- Consider the affected system(s) potentially compromised and plan for full rebuild if critical infrastructure
Sources
- GitHub Advisory GHSA-64m4-w85f-wrjj · GitHub Advisory Database
Cite this entry
"Malware in pump-stream-logger." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed June 26, 2026; last updated June 29, 2026. https://supplychainattack.org/incident/malware-in-pump-stream-logger-wtldv9
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malware in gx-npm-ui
Malware was discovered in the npm package gx-npm-ui, 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 - containedcritical
Malware in @vpms/design-system
Malware was discovered in the npm package @vpms/design-system. 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 - activecritical
Malware in unsafe-malicious-package
Malware discovered in the npm package unsafe-malicious-package. Systems with this package installed are considered fully compromised and require immediate remediation.
npmCompromised package - containedcritical
Malware in ts-ankle
The npm package ts-ankle was found to contain malware. Any system with the package installed or running should be considered fully compromised. All secrets and keys must be rotated from a different computer.
npmCompromised package