Which versions of pretty-logger-utils are malicious?

The following npm versions of pretty-logger-utils are flagged malicious: 1.0.0. Treat any of these as compromised.

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

pretty-logger-utils is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

If pretty-logger-utils 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 pretty-logger-utils across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pretty-logger-utils (version 1.0.0).

Malicious package

pretty-logger-utilsnpm

Advisory published May 20, 2026Updated May 20, 2026

pretty-logger-utils is a confirmed malicious npm package (MAL-2026-4197) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pretty-logger-utils (npm)

MAL-2026-4197

Immediate action

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

npm uninstall pretty-logger-utils

What this malware does

pretty-logger-utils is a malicious npm package that depends on terminal-logger-utils and triggers the malicious behavior in that package when installed or imported.

The terminal-logger-utils payload executes a postinstall hook that opens utils.cjs, an obfuscated malware dropper. The dropper downloads and runs a platform-specific second-stage binary from Hugging Face. The second-stage payload provides keylogger, infostealer, and RAT behavior, steals sensitive local data including Telegram Desktop sessions, browser login databases, crypto wallets, SSH keys, cloud configurations, environment variables, and keyword-matched files, and connects to a remote server for full machine control.

Malicious versions

1 flagged

1.0.0

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for pretty-logger-utils (version 1.0.0).
If you installed it — respond
pretty-logger-utils is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If pretty-logger-utils 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. pretty-logger-utils on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

ox.security

Credits

OX Security · finder

Detect & block this

O3 blocks pretty-logger-utils-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database