Which versions of py-colorprinting are malicious?

The following PyPI versions of py-colorprinting are flagged malicious: 0.1, 0.1.1, 0.1.2, 0.1.3, 0.1.5. Treat any of these as compromised.

How do I remediate py-colorprinting if I installed it?

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

If py-colorprinting 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 py-colorprinting part of a known attack campaign?

Yes — py-colorprinting is associated with the RLMA-2024-11123 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 py-colorprinting across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for py-colorprinting (5 malicious versions).

Malicious package

py-colorprintingPyPI

py-colorprinting is a confirmed malicious PyPI package (MAL-2024-11666) that executes malicious code on install (malicious versions 0.1, 0.1.1, 0.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in py-colorprinting (PyPI)

MAL-2024-11666

Immediate action

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

pip uninstall py-colorprinting

Malicious versions

5 flagged

0.10.1.10.1.20.1.30.1.5

Indicators of compromise (SHA-256)

c023e36c1b8439fa83b79727c915541258c561ea64b82accd76b5ddce92010f2

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for py-colorprinting (5 malicious versions).
If you installed it — respond
Remove py-colorprinting 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 py-colorprinting 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. py-colorprinting on PyPI has been identified as a malicious package (versions 0.1, 0.1.1, 0.1.2, 0.1.3, 0.1.5 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-11123

Credits

ReversingLabs · finder

Detect & block this

O3 blocks py-colorprinting-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