Malicious code in pump-stream-logger (npm)
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (46b661475c354a21044517667315f026469d531e459803f8d4d9586e5cb67f74) The package was found to contain malicious code or consuming dependency that contains malicious code ## Source: ghsa-malware (75034d3c53f657ffc5e0f43c2624e56ae27b9f21c52c17e7d46546223839787c) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
AI Analysis
Technical Summary
The 'pump-stream-logger' package in the npm ecosystem contains malicious code or relies on a dependency that does. This malicious code can fully compromise any computer where the package is installed or running. The compromise includes potential unauthorized access to secrets and keys stored on the system. Due to the severity of the compromise, simple removal of the package does not guarantee full remediation, as attackers may have established persistent control.
Potential Impact
Systems with 'pump-stream-logger' installed or running are considered fully compromised. Attackers may have gained complete control over the system, including access to stored secrets and keys. This can lead to unauthorized data access, credential theft, and further malicious activities. The presence of this package poses a critical security risk.
Mitigation Recommendations
Immediate removal of the 'pump-stream-logger' package is recommended. All secrets and keys stored on the affected system must be rotated from a separate, secure machine. Because the system may be fully compromised, consider rebuilding or restoring the system from a known good backup to ensure complete removal of malicious components.
Malicious code in pump-stream-logger (npm)
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (46b661475c354a21044517667315f026469d531e459803f8d4d9586e5cb67f74) The package was found to contain malicious code or consuming dependency that contains malicious code ## Source: ghsa-malware (75034d3c53f657ffc5e0f43c2624e56ae27b9f21c52c17e7d46546223839787c) Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The 'pump-stream-logger' package in the npm ecosystem contains malicious code or relies on a dependency that does. This malicious code can fully compromise any computer where the package is installed or running. The compromise includes potential unauthorized access to secrets and keys stored on the system. Due to the severity of the compromise, simple removal of the package does not guarantee full remediation, as attackers may have established persistent control.
Potential Impact
Systems with 'pump-stream-logger' installed or running are considered fully compromised. Attackers may have gained complete control over the system, including access to stored secrets and keys. This can lead to unauthorized data access, credential theft, and further malicious activities. The presence of this package poses a critical security risk.
Mitigation Recommendations
Immediate removal of the 'pump-stream-logger' package is recommended. All secrets and keys stored on the affected system must be rotated from a separate, secure machine. Because the system may be fully compromised, consider rebuilding or restoring the system from a known good backup to ensure complete removal of malicious components.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-6507
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-64m4-w85f-wrjj"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a3ef7be27e9c79719ffd517
Added to database: 06/26/2026, 22:05:50 UTC
Last enriched: 07/10/2026, 12:10:01 UTC
Last updated: 07/29/2026, 20:25:38 UTC
Views: 44
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.