# MAL-2026-11195: Malicious code in phabricator-client (PyPI)


- **Type:** Malicious package
- **Package:** `phabricator-client` (PyPI)
- **Published:** 30 Jul 2026

## What is MAL-2026-11195?

MAL-2026-11195 is a malicious package in phabricator-client, published on 30 Jul 2026. 

### Official description

phabricator-client 99.0.4 is a single-file PyPI package whose only runtime effect on import is to resolve lobohunter.duckdns.org and open a TCP connection to port 9999 on that host. The callout is unconditional and fires as soon as the module is imported, leaking the installer's public IP address and confirming code execution on the importing host to the operator of the DuckDNS endpoint. The package ships with placeholder metadata (no description, author, or homepage) and an implausibly inflated version number (99.0.4) intended to win resolution over an internal or lower-versioned package of a similar name — the standard dependency-confusion shape. lobohunter.duckdns.org is a dynamic-DNS host, not a first-party Phabricator endpoint.

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-11195?

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-11195 is a malicious package: phabricator-client (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-11195/ (Markdown: https://insights.sbomify.com/MAL-2026-11195/index.md)
```

## Sources

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

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