Which versions of bpsm are malicious?

The following PyPI versions of bpsm are flagged malicious: 99.0.0. Treat any of these as compromised.

How do I remediate bpsm if I installed it?

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

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

Yes — bpsm is associated with the GENERIC-standard-pypi-install-pentest, GENERIC-hackerone-bugbounty 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 bpsm across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bpsm (version 99.0.0).

Malicious package

bpsmPyPI

Advisory published Mar 9, 2026Updated Apr 10, 2026

bpsm is a confirmed malicious PyPI package (MAL-2026-1296) that steals credentials and exfiltrates sensitive data (malicious version 99.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bpsm (PyPI)

MAL-2026-1296

Immediate action

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

pip uninstall bpsm

What this malware does

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

1 flagged

99.0.0

Indicators of compromise (SHA-256)

5dfe0d38862649d74eb0c306f047d854004293223eae7cfa7f4fc82c9370bd96

05b6d57f9a721bce69dd41f1ddf9cedf05531376ef9b44d1fe87e01dbe39b11d

1dfbedba494f0ed19e351b91c2665df614b8239acd3d2eae479a3e6080c0d454

Detection & response playbook

Credential / info stealer

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

Campaign

GENERIC-standard-pypi-install-pentestGENERIC-hackerone-bugbounty

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

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