Which versions of pycolorom are malicious?

The following PyPI versions of pycolorom are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate pycolorom if I installed it?

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

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

Yes — pycolorom is associated with the 2025-10-speedd-testing-bot 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 pycolorom 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 pycolorom (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging pycolorom across your stack and pipelines.

Malicious package

pycoloromPyPI

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

MAL-2026-96

Immediate action

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

pip uninstall pycolorom

What this malware does

The package, distinguished as a speed testing or typosquatted Telegram library, contains a Telegram bot to perform remote control of the computer

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

Campaign: 2025-10-speedd-testing-bot

Reasons (based on the campaign):

rat
Downloads and executes a remote malicious script.
typosquatting

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

6babcee81c12759b66be4c0a8ba33c3f0272b052a47fda31227f4a6087ba8e5b

52206f99bec4bc356ae9efc68430a8412d28d1e80a7d25a8108dc0acda81c6af

a8c2ce5dba961bbfdc0f303b0a3ec633d35ba030e03bd076a432d1833bf78997

26f5d6d03dee6f6daa76be41653ef85c46e10a2e69c13ac10bc03d9c7576a427

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

Campaign

2025-10-speedd-testing-bot

References

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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