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 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 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?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for terminalbrush (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging terminalbrush across your stack and pipelines.

Malicious package

terminalbrushPyPI

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

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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for terminalbrush (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging terminalbrush across your stack and pipelines.
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 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 terminalbrush 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. 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