Which versions of bettercolors are malicious?

The following PyPI versions of bettercolors are flagged malicious: 0.1.0, 0.1.1, 0.1.2, 0.1.3. Treat any of these as compromised.

How do I remediate bettercolors if I installed it?

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

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

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

Search your lockfiles and build artifacts for bettercolors (4 malicious versions).

Malicious package

bettercolorsPyPI

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

Malicious code in bettercolors (PyPI)

MAL-2024-4796

Immediate action

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

pip uninstall bettercolors

Malicious versions

4 flagged

0.1.00.1.10.1.20.1.3

Indicators of compromise (SHA-256)

3f5dcab718431469b1fd65018ec522cb7bfc6809aef04d554bf69b4cf2747021

468a1801953220728e95413936692ed7aa01ea79e1ef4d833f95484442c83dfd

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-03576RLUA-2024-07855

References

Credits

ReversingLabs · finder

Detect & block this

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