MalwarePublished 14 Jul 2026

@codex2005/logger-core (npm) · Malicious Code

Affects @codex2005/logger-coreSource GCVE Database

Malicious package : remove @codex2005/logger-core and rotate any secrets on hosts that installed it.

Data as of 14 Jul 2026, 09:30 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-10555

What to do

Remove @codex2005/logger-core from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npm@codex2005/logger-core	Affected–	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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.

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.

Defensive guidance

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.

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.

References

github.com/advisories/GHSA-jc68-fr59-2vfv (opens in a new tab)

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Jul 2026, 09:30 UTC

Technical details

References

Community reviews