MAL-2026-6735
Vulnerability from ossf_malicious_packages – Published: 2026-07-02 21:22 – Updated: 2026-07-08 17:03 – Source website| Ecosystem | Package | Versions |
|---|---|---|
| PyPI |
ue-python-tools
|
99999.0.0
|
On import ue_python_tools, the package spawns a background thread that issues an HTTP POST to http://109.123.247.172/pypi carrying a JSON payload composed of the installer's hostname (socket.gethostname()), user identity (os.environ USER/USERNAME), and current working directory (os.getcwd()). The destination is a hardcoded plaintext bare-IP endpoint with no user consent, no configuration surface, and no documented purpose. The package metadata compounds the risk: it is published as version 99999.0.0 with placeholder author 'Security Research' and summary 'Internal package', a version-squat shape designed to be resolved as the 'latest' release by dependency resolvers and to shadow an internal package name via dependency confusion. Installing or importing this package causes installer host identifiers to be transmitted off-machine to an attacker-controlled 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.
| Type | Indicator | Hashes |
|---|---|---|
| Evidence file |
ue_python_tools/__init__.py
|
sha256
7eb358daaafe6a4018476ded21c5a429fcd3fbaf9b17376da07f845e266d774btlsh
4901acc6e8345882524b314888258a382227b8572e03a8b47d4cdf7c0fcc46952b56b8 |
| Evidence file |
setup.py
|
sha256
ca0036e87b4c7ae33dd8a94170de4a40aa68e591c6cba7eff249e9d61d462ad1tlsh
d2d097628e4286a08880889e08a038011a29ad373e31b0d8b38043803f8e0dbdf7326d |
| Package archive |
ue_python_tools-99999.0.0.tar.gz
|
blake2b_256
0862cc55380bde2e1921c94ca81e8591294c8cf9aa740bb24eec0a70ee726ba5md5
a305994038ea26a358688a532a829112sha256
393cbfe0970a8a6d575729a098db5b3a280aeab3d806419834fd957065611b72 |
- 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": "ue_python_tools/__init__.py",
"sha256": "7eb358daaafe6a4018476ded21c5a429fcd3fbaf9b17376da07f845e266d774b",
"tlsh": "4901acc6e8345882524b314888258a382227b8572e03a8b47d4cdf7c0fcc46952b56b8"
},
{
"path": "setup.py",
"sha256": "ca0036e87b4c7ae33dd8a94170de4a40aa68e591c6cba7eff249e9d61d462ad1",
"tlsh": "d2d097628e4286a08880889e08a038011a29ad373e31b0d8b38043803f8e0dbdf7326d"
}
],
"package_integrity": [
{
"filename": "ue_python_tools-99999.0.0.tar.gz",
"hashes": {
"blake2b_256": "0862cc55380bde2e1921c94ca81e8591294c8cf9aa740bb24eec0a70ee726ba5",
"md5": "a305994038ea26a358688a532a829112",
"sha256": "393cbfe0970a8a6d575729a098db5b3a280aeab3d806419834fd957065611b72"
}
}
]
}
},
"package": {
"ecosystem": "PyPI",
"name": "ue-python-tools"
},
"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/ue-python-tools",
"import_time": "2026-07-02T21:29:02.677284358Z",
"modified_time": "2026-07-02T21:22:54.821851Z",
"sha256": "9494382fb3885f95987ec830f096aac6cde589cac9485b6a347bafed9a8a7e39",
"source": "kam193",
"versions": [
"99999.0.0"
]
},
{
"id": "IN-MAL-2026-008129",
"import_time": "2026-07-08T17:01:32.858284043Z",
"modified_time": "2026-07-08T16:28:58Z",
"sha256": "66a6d9d874ce102a9ac674f8f713472a473007dc3d51adb869c5198afc708751",
"source": "amazon-inspector",
"versions": [
"99999.0.0"
]
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (66a6d9d874ce102a9ac674f8f713472a473007dc3d51adb869c5198afc708751)\nOn `import ue_python_tools`, the package spawns a background thread that issues an HTTP POST to http://109.123.247.172/pypi carrying a JSON payload composed of the installer\u0027s hostname (socket.gethostname()), user identity (os.environ USER/USERNAME), and current working directory (os.getcwd()). The destination is a hardcoded plaintext bare-IP endpoint with no user consent, no configuration surface, and no documented purpose. The package metadata compounds the risk: it is published as version 99999.0.0 with placeholder author \u0027Security Research\u0027 and summary \u0027Internal package\u0027, a version-squat shape designed to be resolved as the \u0027latest\u0027 release by dependency resolvers and to shadow an internal package name via dependency confusion. Installing or importing this package causes installer host identifiers to be transmitted off-machine to an attacker-controlled endpoint.\n\n## Source: kam193 (9494382fb3885f95987ec830f096aac6cde589cac9485b6a347bafed9a8a7e39)\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-6735",
"modified": "2026-07-08T17:03:30Z",
"published": "2026-07-02T21:22:54Z",
"references": [
{
"type": "WEB",
"url": "https://bad-packages.kam193.eu/pypi/package/ue-python-tools"
},
{
"type": "PACKAGE",
"url": "https://pypi.org/project/ue-python-tools/99999.0.0/"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in ue-python-tools (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.