Which versions of supercolor-tui are malicious?

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

How do I remediate supercolor-tui if I installed it?

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

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

Yes — supercolor-tui is associated with the 2026-11-chromacli 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 supercolor-tui across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for supercolor-tui (4 malicious versions).

Malicious package

supercolor-tuiPyPI

Advisory published Nov 8, 2026Updated Nov 8, 2026

supercolor-tui is a confirmed malicious PyPI package (MAL-2026-18767) that steals credentials and exfiltrates sensitive data (malicious versions 0.1.0, 0.1.1, 0.1.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in supercolor-tui (PyPI)

MAL-2026-18767

Immediate action

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

pip uninstall supercolor-tui

What this malware does

Package hides a code downloading and installing an infostealer.

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

Campaign: 2026-11-chromacli

Reasons (based on the campaign):

Downloads and executes a remote executable.
malware
infostealer
action-hidden-in-lib-usage

Malicious versions

4 flagged

0.1.00.1.10.1.20.1.4

Indicators of compromise (SHA-256)

9798fa32337256d29d4b551193b6aa6817601034ce787bae4d09d7d6636d813b

0cdf2ba66c33faabd6be6ed36062fb33456f54ff97a408af930eee82f66ba3a2

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for supercolor-tui (4 malicious versions).
If you installed it — respond
supercolor-tui 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 supercolor-tui 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. supercolor-tui on PyPI has been identified as a malicious package (versions 0.1.0, 0.1.1, 0.1.2, 0.1.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-11-chromacli

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks supercolor-tui-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