Which versions of quicolor are malicious?

The following PyPI versions of quicolor are flagged malicious: 9.7.3, 9.8.1, 10.0.0, 10.0.1, 10.0.2, 10.0.3, 10.0.4, 10.0.5, 10.0.6, 10.0.9. Treat any of these as compromised.

How do I remediate quicolor if I installed it?

quicolor is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed quicolor — how do I know if it already compromised me?

If quicolor was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is quicolor part of a known attack campaign?

Yes — quicolor is associated with the RLMA-2025-02526, 2025-03-quicolor, RLUA-2026-00680 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 quicolor across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for quicolor (10 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging quicolor across your stack and pipelines.

Malicious package

quicolorPyPI

Malicious code in quicolor (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-3462

Immediate action

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

pip uninstall quicolor

What this malware does

Importing the module starts a code that exfiltrates data from local Telegram application

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2025-03-quicolor

Reasons (based on the campaign):

exfiltration-generic

Malicious versions

10 flagged

9.7.39.8.110.0.010.0.110.0.210.0.310.0.410.0.510.0.610.0.9

Indicators of compromise (SHA-256)

6992e043da359299c0602007c4171c2812d8fb23710de6962240e111a677e7fe

672dc3cd0bf9a03396ecf3f2a881816efe7517f94912ccbf8aebda5579d66751

4b11a81f135d7d2ac414b7144af73523d15db7b0ce1a2757ba6ba95f50bf0be8

f942292de0d605b8134f722cc3b874a17340ae510ece7c2b942c6553ace9a4f8

5eae13e9042ef97b67fd708be79993f965f6d7eab5ee2881784d05c68ef14aab

fcc46d77ccf7d9617569b7c6468fcbb3aa8db7f7e112ed12bcf336937b94274c

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for quicolor (10 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging quicolor across your stack and pipelines.
If you installed it — respond
quicolor is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If quicolor was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks quicolor before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. quicolor on PyPI has been identified as a malicious package (versions 9.7.3, 9.8.1, 10.0.0, 10.0.1, 10.0.2, 10.0.3, 10.0.4, 10.0.5, and 2 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-025262025-03-quicolorRLUA-2026-00680

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks quicolor-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring