Which versions of termcolour are malicious?

The following PyPI versions of termcolour are flagged malicious: 0.0.1, 3.3.1, 3.3.3. Treat any of these as compromised.

How do I remediate termcolour if I installed it?

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

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

Yes — termcolour is associated with the RLMA-2024-04906, RLUA-2024-09374, RLUA-2025-06595 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 termcolour across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for termcolour (3 malicious versions).

Malicious package

termcolourPyPI

Advisory published Jun 25, 2024Updated Dec 24, 2025

termcolour is a confirmed malicious PyPI package (MAL-2024-6103) that executes malicious code on install (malicious versions 0.0.1, 3.3.1, 3.3.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in termcolour (PyPI)

MAL-2024-6103

Immediate action

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

pip uninstall termcolour

Malicious versions

3 flagged

0.0.13.3.13.3.3

Indicators of compromise (SHA-256)

77c613c1d7ffe5cbff83deb07456de34588d5fd8e0411d6129e170129fc8a5ed

b153d0424e2fd8e0bd965b056e3b6baf311fc91b41c36dff6c850c1eea8f940c

f1e187f97ba67a5062023f8c6bfa03716caefaea4bdc18cd35857ba1728e92be

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for termcolour (3 malicious versions).
If you installed it — respond
Remove termcolour 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 termcolour 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. termcolour on PyPI has been identified as a malicious package (versions 0.0.1, 3.3.1, 3.3.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-04906RLUA-2024-09374RLUA-2025-06595

References

reversinglabs.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks termcolour-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