Malware in log-taker1
The npm package log-taker1 contains malware that grants full control of affected systems. 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 log-taker1 installed or running is considered fully compromised.
- Ecosystems
- Attack vectors
- Affected entities
- log-taker1
The npm package log-taker1 has been identified as containing malware. According to the GitHub Advisory (GHSA-35q5-q365-j23w), 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 package installation, as the attacker may have gained full control of the system.\n\nThis represents a critical supply chain attack through a malicious npm package with broad impact on any system where it was installed or executed.
Indicators of compromise
- Packages
- log-taker1
Remediation
- Immediately isolate any computer with log-taker1 installed or running from the network
- Rotate all secrets, API keys, credentials, and cryptographic keys from a different, uncompromised computer
- Remove the log-taker1 package from all affected systems
- Conduct a full forensic analysis of affected systems to identify any additional malicious software or persistence mechanisms
- Review system logs and network traffic for signs of unauthorized access or data exfiltration
- Consider full system reimaging if full compromise is suspected
Sources
- GitHub Advisory GHSA-35q5-q365-j23w · GitHub Advisory Database
Cite this entry
"Malware in log-taker1." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 27, 2026; last updated July 27, 2026. https://supplychainattack.org/incident/malware-in-log-taker1-1mkx4w
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