nj-logger (npm) · Malicious Code
Affects nj-loggerSource GCVE Database
Malicious package : remove nj-logger and rotate any secrets on hosts that installed it.
Data as of 11 Nov 2026, 02:22 UTC
Malicious package
Published to npm · OSV MAL-2026-2907
What to do
Remove nj-logger 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 |
|---|---|---|
| npmnj-logger | 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 nj-logger contains malicious code that downloads and executes a Windows-specific trojan (W64.AIDetectMalware / Trojan.Malware.300983.susgen) from a remote server. The malicious downloader is obfuscated and disguised as a telemetry module, using base64 and XOR encoding for URLs and paths. Any system with this package installed should be considered fully compromised, and all secrets and keys on that system should be rotated immediately. Removing the package alone may not eliminate the threat due to potential full system compromise.