NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Part of a larger attack: 2024-11-byted-dast published 183 malicious packages. See the full campaign →
Malicious package

libbmetPyPI

Advisory published Updated

libbmet is a confirmed malicious PyPI package (MAL-2024-10641) that steals credentials and exfiltrates sensitive data (malicious version 94.6). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in libbmet (PyPI)

MAL-2024-10641
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
pip uninstall libbmet

What this malware does

A campaign of probably pentest packages flooding PYPI. Installing the package or importing the module triggers reporting basic info like hostname, path and the username to the package author. There is no other purpose of the package.

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: 2024-11-byted-dast

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.

  • typosquatting

  • dependency-confusion

The OpenSSF Package Analysis project identified 'libbmet' @ 94.6 (pypi) as malicious.

It is considered malicious because:

  • The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged
94.6

Indicators of compromise (SHA-256)

4b118556da9e2bba947c48d051cc3cc78b284506ed69b69d2d314bc65e79e6d6
0c2771bea8300dc3fd9b78acb53cb02255828cdaa0e6f60714e3c855664516e3
12e210851a01148bf8927296b30371a140cc028880e07ff392e76c404f2ba3ac
ac65dcd563d06fc1bbec2395b43f3c2d110d2b217e1b1ead96e79509a3d15f8a

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for libbmet (version 94.6).

  2. If you installed it — respond

    libbmet 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.

  3. Did it already run?

    If libbmet 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. libbmet on PyPI has been identified as a malicious package (version 94.6 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2024-11-byted-dast

References

Credits

  • Kamil Mańkowski (kam193)
  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks libbmet-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

libbmet (PyPI) malicious package — MAL-2024-10641 | O3 Security