Which versions of colorona are malicious?

The following PyPI versions of colorona are flagged malicious: 0.2.6. Treat any of these as compromised.

How do I remediate colorona if I installed it?

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

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

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

Malicious package

coloronaPyPI

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

MAL-2025-3443

Immediate action

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

pip uninstall colorona

What this malware does

If the method "SetTerminalColor", imitating colorama package, is called, then the code exfiltrated browser, discord and Minecraft passwords/tokens.

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

Campaign: 2025-04-colorona

Reasons (based on the campaign):

action-hidden-in-lib-usage
typosquatting
exfiltration-browser-data

Malicious versions

1 flagged

0.2.6

Indicators of compromise (SHA-256)

4c2043706fafe095814fd6fbd629c375cb8b0da0584dae5c1ea39fb6e9609a9f

8038b2d9ca6cd50ab1bbe9e0d782e00e22223f7117b4a9188a2edbe2adb0ca70

27014d3a14c4b1df61609aa62f901b3f8cb01f4898bb729d52d6cd08928555be

35a6bace9b6571730a41deaf32dbff44d85503c0516561bd647a7df228b1c3dd

36560d5cd7fb9c68c4a96a0633d8ccf7b5b04041523b795e8931d9c58a5c52bd

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

Campaign

RLMA-2025-025042025-04-coloronaRLUA-2026-00216

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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