MAL-2026-6734
Vulnerability from ossf_malicious_packages – Published: 2026-07-02 21:23 – Updated: 2026-07-08 17:03 – Source website| Ecosystem | Package | Versions |
|---|---|---|
| PyPI |
horde-python-client
|
99999.0.0
|
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.
| Type | Indicator | Hashes |
|---|---|---|
| Evidence file |
horde_python_client/__init__.py
|
sha256
2f180a296cc8490ee65619e18d1c62e85895ad4151ea927389c0e18f9364decftlsh
6e01acc6e8345882628b724888254a782237b4576f02b8b0bd4c9f7c0fdc46952786f8 |
| Evidence file |
setup.py
|
sha256
cadb4d65a9b7ec5edadb1a7352b50f09b3ef3a32115b72f8bc7252d69a72a3a6tlsh
65d097524e4292b058c0c99e48e138021a28aa373e20b0e8f38003803f8e4db8f332a9 |
| Package archive |
horde_python_client-99999.0.0.tar.gz
|
blake2b_256
589c2b73bf17cc40ca0d837bbc6c8feeace5f61931e479bd673812cfd6732c01md5
a6f2c3b63758f3301b161bc75e71e02csha256
c64fc3df904e530585083fd1d0ae3fef410b515b0335d10c1885cd0e75576990 |
- CWE-506 - Embedded Malicious Code
{
"affected": [
{
"database_specific": {
"cwes": [
{
"cweId": "CWE-506",
"description": "The product contains code that appears to be malicious in nature.",
"name": "Embedded Malicious Code"
}
],
"indicators": {
"evidence_files": [
{
"path": "horde_python_client/__init__.py",
"sha256": "2f180a296cc8490ee65619e18d1c62e85895ad4151ea927389c0e18f9364decf",
"tlsh": "6e01acc6e8345882628b724888254a782237b4576f02b8b0bd4c9f7c0fdc46952786f8"
},
{
"path": "setup.py",
"sha256": "cadb4d65a9b7ec5edadb1a7352b50f09b3ef3a32115b72f8bc7252d69a72a3a6",
"tlsh": "65d097524e4292b058c0c99e48e138021a28aa373e20b0e8f38003803f8e4db8f332a9"
}
],
"package_integrity": [
{
"filename": "horde_python_client-99999.0.0.tar.gz",
"hashes": {
"blake2b_256": "589c2b73bf17cc40ca0d837bbc6c8feeace5f61931e479bd673812cfd6732c01",
"md5": "a6f2c3b63758f3301b161bc75e71e02c",
"sha256": "c64fc3df904e530585083fd1d0ae3fef410b515b0335d10c1885cd0e75576990"
}
}
]
}
},
"package": {
"ecosystem": "PyPI",
"name": "horde-python-client"
},
"versions": [
"99999.0.0"
]
}
],
"credits": [
{
"contact": [
"inspector-research@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
},
{
"contact": [
"https://github.com/kam193",
"https://bad-packages.kam193.eu/"
],
"name": "Kamil Ma\u0144kowski (kam193)",
"type": "REPORTER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "pypi/GENERIC-standard-pypi-install-pentest/horde-python-client",
"import_time": "2026-07-02T21:29:02.667033146Z",
"modified_time": "2026-07-02T21:23:53.578472Z",
"sha256": "ad72fe1fdc56e7fb5716a906fb8481bfe1e477d2f97c649d5db853a79130628a",
"source": "kam193",
"versions": [
"99999.0.0"
]
},
{
"id": "IN-MAL-2026-008127",
"import_time": "2026-07-08T17:01:32.704709685Z",
"modified_time": "2026-07-08T16:28:39Z",
"sha256": "f2ae9afcd7af22c82b137c1142ae643502d82f3d1f28712b2e5c7ec412bea85e",
"source": "amazon-inspector",
"versions": [
"99999.0.0"
]
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (f2ae9afcd7af22c82b137c1142ae643502d82f3d1f28712b2e5c7ec412bea85e)\nhorde-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\u0027s 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) \u2014 the canonical shape for overriding a target organization\u0027s 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.\n\n## Source: kam193 (ad72fe1fdc56e7fb5716a906fb8481bfe1e477d2f97c649d5db853a79130628a)\nInstalling the package or importing the module exfiltrates basic information about the host, and the package has no other purpose.\n\n\n---\n\nCategory: PROBABLY_PENTEST - Packages looking like typical pentest packages, but also anything that looks like testing, exploring pre-prepared kits, research \u0026 co, with clearly low-harm possibilities.\n\n\nCampaign: GENERIC-standard-pypi-install-pentest\n\n\nReasons (based on the campaign):\n\n\n - The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.\n\n\n - The package overrides the install command in setup.py to execute malicious code during installation.\n",
"id": "MAL-2026-6734",
"modified": "2026-07-08T17:03:30Z",
"published": "2026-07-02T21:23:53Z",
"references": [
{
"type": "WEB",
"url": "https://bad-packages.kam193.eu/pypi/package/horde-python-client"
},
{
"type": "PACKAGE",
"url": "https://pypi.org/project/horde-python-client/99999.0.0/"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in horde-python-client (PyPI)"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.