phabricator-clientPyPI
phabricator-client is a confirmed malicious PyPI package (MAL-2026-11195) that steals credentials and exfiltrates sensitive data (malicious versions 99.0.0, 99.0.1, 99.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in phabricator-client (PyPI)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for phabricator-client (5 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging phabricator-client across your stack and pipelines.
If you installed it — respond
phabricator-client 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 phabricator-client was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks phabricator-client before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
- Kamil Mańkowski (kam193) · reporter
Detect & block this
O3 blocks phabricator-client-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.