Which versions of bettercolor are malicious?

The following PyPI versions of bettercolor are flagged malicious: 1, 2, 3. Treat any of these as compromised.

How do I remediate bettercolor if I installed it?

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

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

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

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

Malicious package

bettercolorPyPI

bettercolor is a confirmed malicious PyPI package (MAL-2024-4795) that executes malicious code on install (malicious versions 1, 2, 3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bettercolor (PyPI)

MAL-2024-4795

Immediate action

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

pip uninstall bettercolor

Malicious versions

3 flagged

123

Indicators of compromise (SHA-256)

ab82f8fcff2f39f0903305b6e3f8dd15b4a1fa9d84a6e083a0fa50e3afdb2ece

f1ec4271cc6cd13936f5eaaff64ede671c26774461aa0f801edd9296b9581342

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-03575RLUA-2024-07854

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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