Which versions of pipcolouringslibv1 are malicious?

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

How do I remediate pipcolouringslibv1 if I installed it?

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

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

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

Search your lockfiles and build artifacts for pipcolouringslibv1 (2 malicious versions).

Malicious package

pipcolouringslibv1PyPI

pipcolouringslibv1 is a confirmed malicious PyPI package (MAL-2024-5503) that executes malicious code on install (malicious versions 1.0.0, 1.5.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pipcolouringslibv1 (PyPI)

MAL-2024-5503

Immediate action

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

pip uninstall pipcolouringslibv1

Malicious versions

2 flagged

1.0.01.5.1

Indicators of compromise (SHA-256)

fdcb271acf263f5af35083811db5db94d9f2728f00906d80a6bb315d0328d6c4

6b3089fd09d745f585bb8738a3066dffea67e4e91d8e5d7d3897a0f36021f1dd

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-04285RLUA-2024-08713

References

Credits

ReversingLabs · finder

Detect & block this

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