Which versions of coloryi are malicious?

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

How do I remediate coloryi if I installed it?

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

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

Yes — coloryi is associated with the RLMA-2025-02505, 2025-03-quicolor, RLUA-2026-00217 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 coloryi 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 coloryi (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 coloryi across your stack and pipelines.

Malicious package

coloryiPyPI

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

MAL-2025-3444

Immediate action

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

pip uninstall coloryi

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)

f5df6a7eea6d24cbb7db602f935e7c6ad851ce05cf09417f58185791a85841e0

a156ccbecbbf8714cc28f0e7b04de209b289d8583e998512606470b65bb2b1da

7fda5ee85e248eb4ab426d18592fa9703ff19567ed041d3d75740a231464152d

b31669d50a369022e06125b676383ec5c826daf277494b646ad48fc852462315

18051d27596576c1132e8370577d22fbe69bb56b545fbe874613256f50cd3809

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 coloryi (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 coloryi across your stack and pipelines.
If you installed it — respond
coloryi 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 coloryi 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 coloryi 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. coloryi 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-025052025-03-quicolorRLUA-2026-00217

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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