Which versions of coloramapkgsdow are malicious?

The following PyPI versions of coloramapkgsdow are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate coloramapkgsdow if I installed it?

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

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

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

Malicious package

coloramapkgsdowPyPI

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

MAL-2025-5104

Immediate action

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

pip uninstall coloramapkgsdow

What this malware does

Importing the module starts download and running a remote executable, identified as malware by AVs

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

Campaign: 2025-05-coloramashowtemp

Reasons (based on the campaign):

Downloads and executes a remote executable.
malware

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

e8eaff348384a76a23b2d8f149613c9d56d6149e3a73583cebbd37b81fc55a9a

3ea93d109eaee4464d61573448dc1b4e4aa4088dc505603ef31edf7f97d3fb97

e2da29a60f5b387e349146afb12daf99754dd4c0ccdc85e09ab82a272f471873

2c07b8b1a8058a35f094f6baa72e55bca26bfb3b8bbbde78689ddf0373f698cc

1c303ea5a89f3ebb0e627a4e5a727c431f76c221d6951bd580804ea567c1d9f6

bce9ded1f986151c9b421a6ef4e749e4ea8d4616d744397254313e61b3fb74f0

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

Campaign

RLMA-2025-03001RLUA-2025-035682025-05-coloramashowtempRLUA-2026-00209

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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