Which versions of colorame are malicious?

The following PyPI versions of colorame are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate colorame if I installed it?

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

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

Yes — colorame is associated with the RLMA-2024-03706, RLUA-2024-07997 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 colorame across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for colorame (version 1.0.0).

Malicious package

coloramePyPI

colorame is a confirmed malicious PyPI package (MAL-2024-4926) 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 colorame (PyPI)

MAL-2024-4926

Immediate action

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

pip uninstall colorame

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

248f4cd2558491aa4b630585e2de640acc87397ae05175656b9dfe76819141e9

9e0ccca2f3b01669ca35b82934193451f633e0f0da3a653b3ae624afc84d88af

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for colorame (version 1.0.0).
If you installed it — respond
Remove colorame 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 colorame 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. colorame on PyPI 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-2024-03706RLUA-2024-07997

References

Credits

ReversingLabs · finder

Detect & block this

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