Which versions of pretty-cli-logger are malicious?

The following PyPI versions of pretty-cli-logger are flagged malicious: 1.0.0, 1.0.1, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, 1.0.9, 1.1.0, 1.1.1, 1.1.2. Treat any of these as compromised.

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

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

If pretty-cli-logger was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

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

Yes — pretty-cli-logger is associated with the 2025-04-pretty-cli-logger 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 pretty-cli-logger across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pretty-cli-logger (12 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pretty-cli-logger across your stack and pipelines.

Malicious package

pretty-cli-loggerPyPI

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

MAL-2025-191816

Immediate action

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

pip uninstall pretty-cli-logger

What this malware does

Contains an obfuscated code that will download and run a remote script. At the time of the analysis, the remote URLs were delivering empty results

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-04-pretty-cli-logger

Reasons (based on the campaign):

Downloads and executes a remote malicious script.
obfuscation

Malicious versions

12 flagged

1.0.01.0.11.0.31.0.41.0.51.0.61.0.71.0.81.0.91.1.01.1.11.1.2

Indicators of compromise (SHA-256)

e4b404b0a26f6e39e41249ec5c022e9a7be97fbc97f8a4da5174e2a1d0bf2eed

94cd11911ce2a0937d9e56087ce9487db18da5bb20df7f1f8948f8356d65c31d

1554c75dab30f5e43afff67db7412c981ce58b73bb221ce29ac1f006f3ced614

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for pretty-cli-logger (12 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pretty-cli-logger across your stack and pipelines.
If you installed it — respond
pretty-cli-logger 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-cli-logger was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks pretty-cli-logger before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. pretty-cli-logger on PyPI has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.3, 1.0.4, 1.0.5, 1.0.6, 1.0.7, 1.0.8, and 4 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-04-pretty-cli-logger

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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