Which versions of colorinsa are malicious?

The following PyPI versions of colorinsa are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate colorinsa if I installed it?

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

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

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

Malicious package

colorinsaPyPI

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

MAL-2025-3442

Immediate action

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

pip uninstall colorinsa

What this malware does

Using the color function triggers attempts to exfiltrate browsers data

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

Campaign: 2025-04-colorinsa

Reasons (based on the campaign):

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

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2e249c393e5641e2eccea366dc6786fa0aa90450cf4fea6cde8ba048f281aae7

8addb890be366164260c8cb4ecfd98cd5d79cc21092e24c8d2d6353449de7d14

ea605189c0cea53175b8c70e9163dcc15333629a93b9ea991d154486c931950c

1c7364944afd260dda09f906acdbfd6578d7d2f2af0460f0b92e2357d8fd6e86

556212fdfd8f9032865f11ea6c3831dd75797307655c388a087ddfe33803d41e

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

Campaign

RLMA-2025-025032025-04-colorinsaRLUA-2026-00214

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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