Which versions of bash8 are malicious?

The following PyPI versions of bash8 are flagged malicious: 0.0.0, 1.0.0. Treat any of these as compromised.

How do I remediate bash8 if I installed it?

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

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

Yes — bash8 is associated with the GENERIC-standard-pypi-install-pentest, IN-MAL-2026-006658, IN-MAL-2026-006659, IN-MAL-2026-008140 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 bash8 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 bash8 (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bash8 across your stack and pipelines.

Malicious package

bash8PyPI

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

MAL-2026-5768

Immediate action

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

pip uninstall bash8

What this malware does

Package is published as 'bash8' (matching an existing PyPI bash linter) but installs a top-level module named 'ca_certificates' whose only content is a stub __version__ = "0.0.0" and an info() function returning the string 'This is a dummy bash8 package for PyPI.' Author metadata is the placeholder 'Your Name [email protected]'. The package contains no install hooks, no network I/O, no subprocess execution, and no credential reads — it is functionally inert. The installable module name 'ca_certificates' would shadow imports of that identifier in any environment where this package is installed, and the distribution name collides with an existing linter. Name confusion alone, without an installer-harm payload, is a subjective signal best resolved by a human reviewer.

Installing the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.

Category: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research & co, with clearly low-harm possibilities.

Campaign: GENERIC-standard-pypi-install-pentest

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

2 flagged

0.0.01.0.0

Indicators of compromise (SHA-256)

cc82142b2f705e97dabfd2945e1f4686296211b857a6ccda5195803650bddf63

375ef978992bd3c12f8778e62d2c6f8a105fa3a15cc508db6d8dd6043fd7507c

878c40538865804940e8dedf17a905b5f1675c4f495f061fa2615c5382f190fb

e665213ba552605420b2269888e041b8b8af4c9e8314d731a8aa246f0fefd748

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

Campaign

GENERIC-standard-pypi-install-pentestIN-MAL-2026-006658IN-MAL-2026-006659IN-MAL-2026-008140

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

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