Which versions of terminalbrush are malicious?

The following PyPI versions of terminalbrush are flagged malicious: 0.1, 0.2.4. Treat any of these as compromised.

How do I remediate terminalbrush if I installed it?

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

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

Yes — terminalbrush is associated with the 2026-01-old-terminalbrush 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 terminalbrush across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for terminalbrush (2 malicious versions).

Malicious package

terminalbrushPyPI

Advisory published Jan 21, 2026Updated Jan 21, 2026

terminalbrush is a confirmed malicious PyPI package (MAL-2026-444) that steals credentials and exfiltrates sensitive data (malicious versions 0.1, 0.2.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in terminalbrush (PyPI)

MAL-2026-444

Immediate action

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

pip uninstall terminalbrush

What this malware does

Package downloads an executable, places it distinguished as a Python binary and starts it. At the time of analysis, the URL was no longer active, so it was not possible to confirm the exact behaviour.

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

Campaign: 2026-01-old-terminalbrush

Reasons (based on the campaign):

Downloads and executes a remote executable.

Malicious versions

2 flagged

0.10.2.4

Indicators of compromise (SHA-256)

35e06fb41f9c1a4f082cf49a72dec89fc5b4d2f6580b97e527d291d50807b801

Detection & response playbook

Credential / info stealer

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

Campaign

2026-01-old-terminalbrush

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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