Which versions of qtcolor are malicious?

The following PyPI versions of qtcolor are flagged malicious: 2.3, 4.2, 4.3. Treat any of these as compromised.

How do I remediate qtcolor if I installed it?

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

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

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

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

Malicious package

qtcolorPyPI

qtcolor is a confirmed malicious PyPI package (MAL-2024-5845) that executes malicious code on install (malicious versions 2.3, 4.2, 4.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in qtcolor (PyPI)

MAL-2024-5845

Immediate action

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

pip uninstall qtcolor

Malicious versions

3 flagged

2.34.24.3

Indicators of compromise (SHA-256)

282e22f73be7b4ac6a4fb7b665ef8206877c2c7e05e8ea1b08d93635ade8e18d

e206555d348d4ff88426761c5a48e4295417eee552fa2a7560efbf4616a63897

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-04646RLUA-2024-09100

References

Credits

ReversingLabs · finder

Detect & block this

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