Which versions of cli-pretty-logger are malicious?

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

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

Remove cli-pretty-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 cli-pretty-logger — how do I know if it already compromised me?

If cli-pretty-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.

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

Yes — cli-pretty-logger is associated with the RLMA-2026-05025, RLUA-2026-06155 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

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

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

Malicious package

cli-pretty-loggernpm

Advisory published Jul 7, 2026Updated Sep 1, 2026

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

Malicious code in cli-pretty-logger (npm)

MAL-2026-7246

Immediate action

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

npm uninstall cli-pretty-logger

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

cbc92054643f0316cf729be245c045b3b8bb23a06726762495762bf24b5d60a5

a27833bde23a3b5990f843893f26458a531b96068cca8a0c0f8a6ba8fde79752

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for cli-pretty-logger (version 1.0.0).
If you installed it — respond
Remove cli-pretty-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 cli-pretty-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. cli-pretty-logger 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.

Campaign

RLMA-2026-05025RLUA-2026-06155

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks cli-pretty-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