MalwarePublished 13 Nov 2026

winston-loggerex (npm) · Malicious Code

Affects winston-loggerexSource GCVE Database

Malicious package : remove winston-loggerex and rotate any secrets on hosts that installed it.

Data as of 13 Nov 2026, 05:57 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-19218

What to do

Remove winston-loggerex 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
npmwinston-loggerex	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 winston-loggerex npm package contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected system should be rotated immediately from a different, trusted machine. Removing the package alone may not fully remediate the infection, as the attacker may have established persistent control over the system.

Impact

Full system compromise on any computer running or having installed the winston-loggerex package. All stored secrets and keys on the compromised system are at risk and must be rotated. The attacker may maintain persistent access even after package removal.

Defensive guidance

Immediately remove the winston-loggerex package from all affected systems. Rotate all secrets and keys stored on compromised machines from a different, secure computer. Consider the affected systems fully compromised and perform thorough incident response and remediation beyond just package removal.

Summary

The winston-loggerex package distributed via npm has been identified as containing malicious code. Installation or execution of this package results in a full compromise of the host system, potentially allowing an attacker to gain complete control. Due to the severity of the compromise, all sensitive credentials on the affected machine must be considered exposed and rotated from a secure environment. The package removal does not guarantee elimination of all malicious artifacts or backdoors introduced by the attacker.

References

github.com/advisories/GHSA-rvgp-2hwx-w3mq (opens in a new tab)

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Nov 2026, 05:57 UTC

Technical details

References

Community reviews