Which versions of colorm are malicious?

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

How do I remediate colorm if I installed it?

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

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

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

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

Malicious package

colormPyPI

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

MAL-2024-4968

Immediate action

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

pip uninstall colorm

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

eb707bb0b89718450947d2ddf57e69982fb87a3b1d81a54c6b4bdb90f24be37f

358e92ba0befa92670b3822f1ac3035d1c1b2a0313948c9eb7f431565a8dc776

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for colorm (version 1.0.0).
If you installed it — respond
Remove colorm 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 colorm 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. colorm 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-03748RLUA-2024-08040

References

Credits

ReversingLabs · finder

Detect & block this

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