Which versions of coloraiz are malicious?

The following PyPI versions of coloraiz are flagged malicious: 1.0.1, 1.0.2, 1.0.3. Treat any of these as compromised.

How do I remediate coloraiz if I installed it?

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

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

Yes — coloraiz is associated with the RLMA-2025-02999, RLUA-2025-03566, 2025-05-coloraiz, RLUA-2026-00207 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 coloraiz 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 coloraiz (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging coloraiz across your stack and pipelines.

Malicious package

coloraizPyPI

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

MAL-2025-5102

Immediate action

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

pip uninstall coloraiz

What this malware does

The package imitates colorama, and places a proxy object over the original colorama module that on every usage executes a remote code. The remote script installs a backdoor through legitimate tunnelling software and upload access credentials to the attacker.

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

Campaign: 2025-05-coloraiz

Reasons (based on the campaign):

impersonation
clones-real-package
action-hidden-in-lib-usage
backdoor
Downloads and executes a remote malicious script.

Malicious versions

3 flagged

1.0.11.0.21.0.3

Indicators of compromise (SHA-256)

9ea259f4f90a9ba1877acd31cdbe71bc8600e20a2cb9b83ba830cbac7df1ce4b

1a7ffe6fe6d8fd9746f01735fc68e8d4a9d8bd7ab89a54c16b6a7e1bebcf8b5e

6a81e133153e897e581658ea617c5256010587413cda88c2b6670c127291e39e

dc4606b3e3f05632a889906f4c259e329a08308382fbc27329752eb8ea6a6c3c

a9c7340f11b6c6b930c65d277226188952f3c0d49712726a4d9e78113ad152d4

4f1b59ad5f047d550901ab3a30b5d6f663fea92b8ff764d6c327165b6a156363

1e4bed8653ea80abff62d06ad621c9ca63f0b99aab9110b98f2b1ae2c5b08ee0

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

Campaign

RLMA-2025-02999RLUA-2025-035662025-05-coloraizRLUA-2026-00207

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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