Which versions of terminalcolornew are malicious?

The following PyPI versions of terminalcolornew are flagged malicious: 0.0.1, 0.0.2, 0.0.3. Treat any of these as compromised.

How do I remediate terminalcolornew if I installed it?

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

If terminalcolornew was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is terminalcolornew part of a known attack campaign?

Yes — terminalcolornew is associated with the 2025-09-consolecolornew 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 terminalcolornew across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for terminalcolornew (3 malicious versions).

Malicious package

terminalcolornewPyPI

Advisory published Sep 16, 2025Updated Dec 31, 2025

terminalcolornew is a confirmed malicious PyPI package (MAL-2025-191892) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.1, 0.0.2, 0.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in terminalcolornew (PyPI)

MAL-2025-191892

Immediate action

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

pip uninstall terminalcolornew

What this malware does

If used, the code attempts to take a photo using the computer's camera and exfiltrates it

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

Campaign: 2025-09-consolecolornew

Reasons (based on the campaign):

exfiltration-generic
action-hidden-in-lib-usage
other

Malicious versions

3 flagged

0.0.10.0.20.0.3

Indicators of compromise (SHA-256)

82c15cda0d072e110044e7aa0628720837f4db8ee05260328af95e91472377b4

5a555882888b9895fbe7575cc6121cad44600e17fb64d7551cacc33b29f2ae9f

8a10f3f13adae7d614f3522802ab54d769f6701903cf08d2224cd9670bf01bed

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for terminalcolornew (3 malicious versions).
If you installed it — respond
terminalcolornew 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 terminalcolornew was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. terminalcolornew on PyPI has been identified as a malicious package (versions 0.0.1, 0.0.2, 0.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-09-consolecolornew

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database