Malicious code in @codex2005/logger-core (npm)
The npm package @codex2005/logger-core contains malicious code that compromises any computer on which it is installed or running. The presence of this package indicates a full system compromise, requiring immediate rotation of all secrets and keys from a separate, trusted machine. Simply removing the package does not guarantee removal of all malicious software introduced by it.
AI Analysis
Technical Summary
The @codex2005/logger-core package on npm is identified as containing malicious code. Installation or execution of this package results in a full compromise of the affected system, potentially allowing an attacker complete control. Due to the severity of the compromise, all credentials and secrets stored on the system must be rotated immediately from a different, secure environment. Removal of the package alone is insufficient to ensure system integrity, as the attacker may have installed additional persistent malicious components.
Potential Impact
Any system with this package installed or running should be considered fully compromised. Attackers may have gained full control over the system, risking exposure or theft of all stored secrets and keys. The compromise undermines system confidentiality, integrity, and availability.
Mitigation Recommendations
Remove the @codex2005/logger-core package immediately. Rotate all secrets and keys from a separate, secure computer to prevent further unauthorized access. Because the system may be fully compromised, consider rebuilding the affected system from a known clean state to ensure complete removal of malicious components. No official patch or fix is available as this is a malicious package rather than a vulnerability in legitimate software.
Malicious code in @codex2005/logger-core (npm)
Description
The npm package @codex2005/logger-core contains malicious code that compromises any computer on which it is installed or running. The presence of this package indicates a full system compromise, requiring immediate rotation of all secrets and keys from a separate, trusted machine. Simply removing the package does not guarantee removal of all malicious software introduced by 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 @codex2005/logger-core package on npm is identified as containing malicious code. Installation or execution of this package results in a full compromise of the affected system, potentially allowing an attacker complete control. Due to the severity of the compromise, all credentials and secrets stored on the system must be rotated immediately from a different, secure environment. Removal of the package alone is insufficient to ensure system integrity, as the attacker may have installed additional persistent malicious components.
Potential Impact
Any system with this package installed or running should be considered fully compromised. Attackers may have gained full control over the system, risking exposure or theft of all stored secrets and keys. The compromise undermines system confidentiality, integrity, and availability.
Mitigation Recommendations
Remove the @codex2005/logger-core package immediately. Rotate all secrets and keys from a separate, secure computer to prevent further unauthorized access. Because the system may be fully compromised, consider rebuilding the affected system from a known clean state to ensure complete removal of malicious components. No official patch or fix is available as this is a malicious package rather than a vulnerability in legitimate software.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- MAL-2026-10555
- Osv Schema Version
- 1.7.4
- Aliases
- ["GHSA-jc68-fr59-2vfv"]
- Ecosystems
- ["npm"]
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a55ff5968715ace432f0997
Added to database: 07/14/2026, 09:20:25 UTC
Last enriched: 07/14/2026, 09:30:01 UTC
Last updated: 07/25/2026, 18:02:22 UTC
Views: 11
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.