Which versions of instantcolor are malicious?

The following PyPI versions of instantcolor are flagged malicious: 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8. Treat any of these as compromised.

How do I remediate instantcolor if I installed it?

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

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

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

Search your lockfiles and build artifacts for instantcolor (7 malicious versions).

Malicious package

instantcolorPyPI

instantcolor is a confirmed malicious PyPI package (MAL-2024-5271) that executes malicious code on install (malicious versions 0.0.2, 0.0.3, 0.0.4…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in instantcolor (PyPI)

MAL-2024-5271

Immediate action

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

pip uninstall instantcolor

Malicious versions

7 flagged

0.0.20.0.30.0.40.0.50.0.60.0.70.0.8

Indicators of compromise (SHA-256)

3e49ba62d9ed16a2464cfa577fedb68d19bca3b18c7993ba16b9d44c634d305c

c16c2181665332e1def7c9fa4c8256ffbf36a0de1633db9a749cc4d33f780574

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-04053RLUA-2024-08413

References

research.jfrog.com

Credits

ReversingLabs · finder

Detect & block this

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