Which versions of coloramapkgsw are malicious?

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

How do I remediate coloramapkgsw if I installed it?

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

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

Yes — coloramapkgsw is associated with the RLMA-2025-03002, RLUA-2025-03569, 2025-05-coloramashowtemp, RLUA-2026-00210 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 coloramapkgsw 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 coloramapkgsw (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 coloramapkgsw across your stack and pipelines.

Malicious package

coloramapkgswPyPI

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

MAL-2025-5105

Immediate action

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

pip uninstall coloramapkgsw

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)

a5a1bce3d73a33b35cc22c3adb85d426b54c206f902db75ecb68569c314447e4

9c0012ed93dcccfd3ba55fc7e501d37c4f5b16c34204bfa5f784a7d009ad2d96

5435abe63645276c4ddc7940bb2a075cf2ca85803a47c2727402f9376c2f3421

d3b0703e237935a2a53d99b6e3ad717e1e604c218e5e21c97773615373adea16

7f9951b8768f4c35b07ebe35b0483757c3ff198140c55ca19b94bed3e0f8a3ac

933e907223a79d56dd099b18d882f2832c09791b516b96a389640b5e92723846

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 coloramapkgsw (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 coloramapkgsw across your stack and pipelines.
If you installed it — respond
coloramapkgsw 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 coloramapkgsw 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 coloramapkgsw 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. coloramapkgsw 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-03002RLUA-2025-035692025-05-coloramashowtempRLUA-2026-00210

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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