Which versions of colorss are malicious?

The following PyPI versions of colorss are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate colorss if I installed it?

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

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

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

Malicious package

colorssPyPI

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

MAL-2026-619

Immediate action

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

pip uninstall colorss

What this malware does

Package silently executes in background a remote script. During the analysis, the script was not accessible

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

Campaign: 2026-02-colorss

Reasons (based on the campaign):

typosquatting
Downloads and executes a remote malicious script.

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

de8be235bf17ee738265f4a0254263fc0caeefa1f9228c9f6f122dfd7b2fac2d

5183bf5a7f0672f53ec3f08c820475ea4882ccf1b4e48564e804d85783eebf10

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

Campaign

2026-02-colorss

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst

Detect & block this

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