Which versions of nj-logger are malicious?

Every published version of nj-logger on npm is considered malicious. Remove the package entirely.

How do I remediate nj-logger if I installed it?

Remove nj-logger from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed nj-logger — how do I know if it already compromised me?

If nj-logger was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

How do I find nj-logger across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for nj-logger (all published versions).

Malicious package

nj-loggernpm

Advisory published Apr 16, 2026Updated Apr 23, 2026

nj-logger is a confirmed malicious npm package (MAL-2026-2907) that executes malicious code on install. Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nj-logger (npm)

MAL-2026-2907

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall nj-logger

What this malware does

nj-logger is a malicious npm package that when imported in file dist/logger/telemetry.js downloads a trojan (for Windows only, W64.AIDetectMalware / Trojan.Malware.300983.susgen) from http://178.128.88[.]40:8080/download/svc to path node_modules/.cache/nj-logger/nj-transport-win32-x64.node and executes it. Downloader is obfuscated as telemetry module, urls & paths are base64 and XOR encoded.

The package nj-logger was found to contain malicious code.

Malicious versions

all versions

Every published version of this package is considered malicious — remove it entirely.

Indicators of compromise (SHA-256)

35414b2bda6d20336301bfdc5c0147a6434ee0e712f1fd5962a61ef34d6e53e9

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for nj-logger (all published versions).
If you installed it — respond
Remove nj-logger from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If nj-logger was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. nj-logger on npm has been identified as a malicious package (all published versions flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

Amazon Inspector · finder
indece · finder

Detect & block this

O3 blocks nj-logger-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database