Malicious Code Exfiltration in bpsm Package

bpsm Updated 09 Mar 2026

Summary

09/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1296: Malicious code in bpsm (PyPI). Affects bpsm versions 99.0.0. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The bpsm package, available on PyPI, is designed for basic system operations. However, it has been identified as malicious due to its capability to exfiltrate sensitive information from the host system, such as IP addresses and usernames. This vulnerability arises from the package's design, which overrides the installation command to execute harmful code during installation.

Vulnerability Detail

The vulnerability in the bpsm package originates from its malicious code that exfiltrates basic data from the host system. When the package is installed or imported, it executes code that collects sensitive information without the user's consent. The primary technical aspect of this vulnerability is the overridden install command in the setup.py file, which allows the execution of this malicious code during the installation process. This poses a risk to users as their system information can be compromised.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

pip uninstall bpsm

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a workaround, users should avoid installing the bpsm package altogether. If it has already been installed, it can be removed using the command: pip uninstall bpsm.

Conclusion

The bpsm package poses a significant risk due to its malicious code that exfiltrates sensitive information from the host system. Users are advised to uninstall the package and monitor their systems for any unauthorized access. Utilizing tools like Vulert can help in identifying such vulnerabilities in real-time.

See every vulnerability recorded for bpsm →

Share this vulnerability

FAQ

The bpsm package is a Python package available on PyPI that is intended for basic system operations but has been identified as malicious.

The bpsm package exfiltrates basic information such as the host's IP address and username.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.

The best prevention is to avoid installing the bpsm package and to monitor your dependencies for any malicious packages.

If you have installed the bpsm package, you should uninstall it immediately using the command: pip uninstall bpsm.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

pip uninstall bpsm

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback