Which versions of pretty-logger-js are malicious?

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

How do I remediate pretty-logger-js if I installed it?

Remove pretty-logger-js 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 network activity or persistence. Use O3 Security's dependency scanner to confirm the package and its artifacts are fully purged across your stack.

Is pretty-logger-js part of a known attack campaign?

Yes — pretty-logger-js is associated with the GHSA-qfx3-7369-9f9v campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

Can O3 Security detect pretty-logger-js in my codebase?

Yes. O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, blocking pretty-logger-js and packages like it before any post-install script runs.

Malicious package

pretty-logger-jsnpm

Malicious code in pretty-logger-js (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-2908

Immediate action

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

npm uninstall pretty-logger-js

What this malware does

pretty-logger-js is a malicious npm package that when imported downloads and executes a C2 dropper from https://www.jsonkeeper[.]com/b/OTOAQ.

The package pretty-logger-js was found to contain malicious code.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

all versions

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

Indicators of compromise (SHA-256)

29e46da449e6d21efcef5e9975a2f8e90c31369882800ed4c560ae47ade99b53

fddf613128c296f64ec393e7904c9889ec40fd4f098317a80f31b336a2cc0847

Frequently asked questions

No. pretty-logger-js 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.

Campaign

GHSA-qfx3-7369-9f9v

References

github.com

Credits

Amazon Inspector · finder
indece · finder

Scan your dependencies

O3 Security blocks malicious packages like this at install time and in CI.

Supply-chain protection