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 fetch-runtime
Malware was discovered in the npm package fetch-runtime. Any system 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 - resolvedcritical
Malicious code in ghazaly (npm)
The npm package ghazaly version 99.9.0 contained malicious code that executed a postinstall hook to collect system information (hostname, current user, IP addresses) and exfiltrate it to a Burp Collaborator domain. The package exhibited dependency-confusion characteristics with a high version number and nonsense dependencies.
npmCompromised packageDependency confusion - containedcritical
Malicious code in base65-13x (npm)
base65-13x@5.0.2 on npm contains malicious obfuscated code disguised as a legitimate base-x library. The decode() function executes a ~123KB VM-style payload with dynamic code construction and network I/O capabilities.
npmCompromised package - containedcritical
Malicious code in kit-vim-map (npm)
The npm package kit-vim-map contained malicious code that executes a remote-controlled Linux ELF binary on installation, providing the attacker with arbitrary RCE, persistence, and file exfiltration capabilities. The binary beacons to C2 server 217.60.77.63 and establishes persistence via systemd user units.
npmCompromised packageMalicious commit