Which versions of quickcolors are malicious?

The following PyPI versions of quickcolors are flagged malicious: 10.0.9. Treat any of these as compromised.

How do I remediate quickcolors if I installed it?

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

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

Yes — quickcolors is associated with the RLMA-2025-02525, 2025-03-quicolor, RLUA-2026-00679 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 quickcolors 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 quickcolors (version 10.0.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging quickcolors across your stack and pipelines.

Malicious package

quickcolorsPyPI

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

MAL-2025-3461

Immediate action

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

pip uninstall quickcolors

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

1 flagged

10.0.9

Indicators of compromise (SHA-256)

f7f33180844bf21d4e3b4dd508c0814debac6577f98a3117429648213fb8a88d

5d56cfce40f395501c69be9623d2beeddca4ea3718c80b34b399ab4b8d966860

05deb6781dc1a1781e9a811200127704052a70029ade2a3e97f2c010d9453fc2

131f70c487d608015b2d16665ed5aaf308ebfe12e7dac94f8e0ab9ee8642dc80

bde02ae74149b630dcf029cdd3b6be4983c8cf26d7b6df34a8529c1415f64506

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 quickcolors (version 10.0.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging quickcolors across your stack and pipelines.
If you installed it — respond
quickcolors 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 quickcolors 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 quickcolors 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. quickcolors on PyPI has been identified as a malicious package (version 10.0.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-025252025-03-quicolorRLUA-2026-00679

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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