Malware in @codex2005/logger-core
Malware was discovered in the npm package @codex2005/logger-core. Systems with this package installed or running should be considered fully compromised, with all secrets and keys requiring immediate rotation from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @codex2005/logger-core
A malicious package named @codex2005/logger-core was published to npm and contains malware. According to the GitHub Advisory (GHSA-jc68-fr59-2vfv), 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 system. 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\nUsers should treat any system that has run this package as potentially compromised and take appropriate incident response measures.
Indicators of compromise
- Packages
- @codex2005/logger-core
Remediation
- Immediately rotate all secrets, API keys, and credentials from a different, uncompromised computer
- Remove the @codex2005/logger-core package from all systems
- Audit system logs and file integrity for signs of additional malicious activity
- Consider full system reimaging or replacement if the package was installed on production or sensitive systems
- Review npm audit logs and dependency trees to identify all affected systems
- Monitor affected systems for suspicious activity even after package removal
Sources
- GitHub Advisory GHSA-jc68-fr59-2vfv · GitHub Advisory Database
Cite this entry
"Malware in @codex2005/logger-core." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed July 14, 2026; last updated July 14, 2026. https://supplychainattack.org/incident/malware-in-codex2005-logger-core-dp3u6e
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