Which versions of horde-python-client are malicious?

The following PyPI versions of horde-python-client are flagged malicious: 99999.0.0. Treat any of these as compromised.

How do I remediate horde-python-client if I installed it?

horde-python-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.

I already installed horde-python-client — how do I know if it already compromised me?

If horde-python-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.

Is horde-python-client part of a known attack campaign?

Yes — horde-python-client is associated with the GENERIC-standard-pypi-install-pentest, IN-MAL-2026-008127 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find horde-python-client across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for horde-python-client (version 99999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging horde-python-client across your stack and pipelines.

Malicious package

horde-python-clientPyPI

Malicious code in horde-python-client (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-6734

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall horde-python-client

What this malware does

horde-python-client 99999.0.0 is a dependency-confusion lure. On import horde_python_client, a daemon thread unconditionally POSTs a JSON payload containing the host's hostname, the USER/USERNAME environment variable, and the current working directory to http://109.123.247.172/pypi over plain HTTP. The destination is a bare IP unrelated to any legitimate package publisher. The package ships with placeholder metadata (description "Internal package", author "Security Research") and an absurdly high version number (99999.0.0) — the canonical shape for overriding a target organization's private package of the same name in resolver precedence. Installer harm: any developer or build system that resolves this package and imports it leaks host identifiers to the attacker, confirming a successful dependency-confusion hit and enabling follow-on targeting.

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

1 flagged

99999.0.0

Indicators of compromise (SHA-256)

ad72fe1fdc56e7fb5716a906fb8481bfe1e477d2f97c649d5db853a79130628a

f2ae9afcd7af22c82b137c1142ae643502d82f3d1f28712b2e5c7ec412bea85e

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for horde-python-client (version 99999.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging horde-python-client across your stack and pipelines.
If you installed it — respond
horde-python-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 horde-python-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 horde-python-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

No. horde-python-client on PyPI has been identified as a malicious package (version 99999.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GENERIC-standard-pypi-install-pentestIN-MAL-2026-008127

References

Credits

Amazon Inspector · finder
Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks horde-python-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.

Malware detection Runtime egress monitoring