Which versions of colorbytes are malicious?

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

How do I remediate colorbytes if I installed it?

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

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

Yes — colorbytes is associated with the RLMA-2024-08018, 2024-08-old-colorbytes, RLUA-2026-00212 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 colorbytes 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 colorbytes (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging colorbytes across your stack and pipelines.

Malicious package

colorbytesPyPI

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

MAL-2024-9962

Immediate action

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

pip uninstall colorbytes

What this malware does

Extremely obfuscated code starts when importing the module, and then downloads the next stages and configuration from pastebin. They include a whole range of infostealer activity, from exfiltrating browser files up to a keylogger and registering mouse clicks.

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

Campaign: 2024-08-old-colorbytes

Reasons (based on the campaign):

obfuscation
Downloads and executes a remote executable.
crypto-related
infostealer

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

8a56539943a10b763ff4f1bc5a62dc4362fc4715f21e728c9c033e29ae5a11fb

d93e7f301249423b016f93f47615a5a403640cc069c10e29630dad381adacf2e

aa4677648d784f5460e80091c656719fc082e6ed9028940b407c97b0e78ff008

f450925ef3e67dbcddad18020f2d442ac8732fdd79d84a4ef60eb15d5091aaf9

157a22714107b31e25dc43e11905d416f8417e77fc8bd3fb52943840d74e2fd7

d0cc09f53bce466ffe28a700f8b7816355f51f603022a18dec203e3c7051c0c5

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

Campaign

RLMA-2024-080182024-08-old-colorbytesRLUA-2026-00212

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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