Which versions of colorizetext are malicious?

The following PyPI versions of colorizetext are flagged malicious: 0.1.0, 0.1.1, 0.1.2, 0.1.3, 0.1.4. Treat any of these as compromised.

How do I remediate colorizetext if I installed it?

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

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

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

Malicious package

colorizetextPyPI

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

MAL-2025-2949

Immediate action

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

pip uninstall colorizetext

What this malware does

Package has a hidden code starting an infostealer

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

Campaign: 2025-03-colorizetext

Reasons (based on the campaign):

infostealer
obfuscation

Malicious versions

5 flagged

0.1.00.1.10.1.20.1.30.1.4

Indicators of compromise (SHA-256)

73aea433df0f3c717cbafc462b62b8a8c48e475c4b82544d869bb5de4aa3d7c7

ea918aef023cdba6e2d62f4227124588059de8955cadeed028abb62bd23202d0

23bf8532a92e751d1429028961f8b21697466cf5938e629cd11105928584f017

6f5a82809c3a2708e443d4b2165197010ba23d478f8f7d67f0903995bd9390f8

e2f6bc5636189c5d92fa41ed47e9d7cab6883c71b87371d52e1f60a861d38e91

51bb17dac846ecd1e51cf07e3c69749be0343a2cc552f459504c9514541c40e6

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

Campaign

RLMA-2025-019472025-03-colorizetextRLUA-2026-00215RLUA-2026-02068

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

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