# MAL-2026-16377: Malicious code in cloushaar-poc-exfil-91827 (PyPI)


- **Type:** Malicious package
- **Package:** `cloushaar-poc-exfil-91827` (PyPI)
- **Published:** 22 Sep 2026

## What is MAL-2026-16377?

MAL-2026-16377 is a malicious package in cloushaar-poc-exfil-91827, published on 22 Sep 2026. 

### Official description

The package's setup.py, executed automatically during pip install, iterates a hardcoded list of installer-side filesystem paths (/flag, /flag.txt, /app/flag, /root/flag, and similar candidates), reads their contents, and transmits them via urllib.request.urlopen as a query-string parameter to the hardcoded endpoint https://webhook.site/f41d2013-dd84-4139-85f8-8e989e0761b8. The webhook.site host is an anonymous request-collector controlled by whoever provisioned that endpoint. The name and version suggest a proof-of-concept exfiltration package, but the shipped code performs real install-time filesystem reads and outbound HTTP exfiltration against any host that runs pip install on this artifact.

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.

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

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-16377 is a malicious package: cloushaar-poc-exfil-91827 (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-16377/ (Markdown: https://insights.sbomify.com/MAL-2026-16377/index.md)
```

## Sources

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

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