Which versions of colorina are malicious?

The following PyPI versions of colorina are flagged malicious: 0.1.0, 0.1.2, 0.1.3, 0.1.4, 0.1.5, 0.1.6, 0.2.0, 0.2.2, 0.2.3, 0.2.4, 0.2.5. Treat any of these as compromised.

How do I remediate colorina if I installed it?

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

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

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

Malicious package

colorinaPyPI

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

MAL-2025-3441

Immediate action

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

pip uninstall colorina

What this malware does

Using the "color" function will exfiltrated data like discord tokens, browser-saved passwords and Minecraft access tokens

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

Campaign: 2025-04-colorina

Reasons (based on the campaign):

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

Malicious versions

11 flagged

0.1.00.1.20.1.30.1.40.1.50.1.60.2.00.2.20.2.30.2.40.2.5

Indicators of compromise (SHA-256)

31aadc2172d1e9969ff4dbdc95124525c61dc5df9faeac8ceba2e4cf60f4744f

96f6290f5c4cb010eab3654f3a50a3a7d4d29f238e9deb28781a2ce319d1b549

5280fa2df728b98c1eda6d86d4b0fc233d4bd0d58ac17160427e16f1bb154081

0fc31d68e7eace5995e48f0ebad0b3f8e8a4a64bfca16a682490666648ff634b

1b35e839e676eef56701f11ca8338200fd40b768d791a656587a7590d016639c

24fcce4c030a398e6b412b8ceadf388322cf81a5c925d3266b9fec42d01d2566

5de4be14c8ab2a7cbf06e5ef3cba1670d49da23d87e7e4a89ef1de4bf14095bb

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

Campaign

RLMA-2025-025022025-04-colorinaRLUA-2026-00213RLUA-2026-02067

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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