MAL-2026-16142
Vulnerability from ossf_malicious_packages – Published: 2026-09-12 09:15 – Updated: 2026-09-23 05:20 – Source website| Ecosystem | Package | Versions |
|---|---|---|
| PyPI |
python-fork
|
0.1.00.1.1
|
The package was found to contain malicious code or consuming dependency that contains malicious code
Importing the module starts a fork bomb, what can lead to destabilizing the system.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-09-python-fork
Reasons (based on the campaign):
- other
| Type | Indicator | Hashes |
|---|---|---|
| Evidence file |
python_fork/main.py
|
sha256
9b41d818a167786cd623deace02a5bc9cc52682abd60b562f28d6fccecee3178 |
| Package archive |
python_fork-0.1.0-py3-none-any.whl
|
blake2b_256
d8262caa51663d203cb1814c27469b92b839cd898dfe05ddbfce7dfb1346a9fdmd5
32313b22ae7129835897b156593c56c1sha256
4be839959f96d71a2df7a4b1c48d7866f0e3cdf5f1f581ffd6cfdcf3474e541a |
| Package archive |
python_fork-0.1.0.tar.gz
|
blake2b_256
8f173cee75c536d667415e8ca254915b8ff2043ac95b0cd2bf59a2eaafe8296fmd5
c152d5b6c9543fca17c3efb2a805f453sha256
13a753b6aa92cf8a311b258ffa1b5c984cca0cf39d757402169c7ec87f2e11d9 |
- 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": "python_fork/main.py",
"sha256": "9b41d818a167786cd623deace02a5bc9cc52682abd60b562f28d6fccecee3178"
}
],
"package_integrity": [
{
"filename": "python_fork-0.1.0-py3-none-any.whl",
"hashes": {
"blake2b_256": "d8262caa51663d203cb1814c27469b92b839cd898dfe05ddbfce7dfb1346a9fd",
"md5": "32313b22ae7129835897b156593c56c1",
"sha256": "4be839959f96d71a2df7a4b1c48d7866f0e3cdf5f1f581ffd6cfdcf3474e541a"
}
},
{
"filename": "python_fork-0.1.0.tar.gz",
"hashes": {
"blake2b_256": "8f173cee75c536d667415e8ca254915b8ff2043ac95b0cd2bf59a2eaafe8296f",
"md5": "c152d5b6c9543fca17c3efb2a805f453",
"sha256": "13a753b6aa92cf8a311b258ffa1b5c984cca0cf39d757402169c7ec87f2e11d9"
}
}
]
}
},
"package": {
"ecosystem": "PyPI",
"name": "python-fork"
},
"versions": [
"0.1.0",
"0.1.1"
]
}
],
"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/2026-09-python-fork/python-fork",
"import_time": "2026-09-12T10:15:50.493268624Z",
"modified_time": "2026-09-12T09:15:57.654803Z",
"sha256": "0bff88696e931354b786185cde4b21e28c27407203c5733ac31b52b7186c1e78",
"source": "kam193",
"versions": [
"0.1.0",
"0.1.1"
]
},
{
"id": "IN-MAL-2026-020471",
"import_time": "2026-09-23T05:18:37.076246547Z",
"modified_time": "2026-09-23T05:12:06Z",
"sha256": "ccd1d960319085a4aee1c389c4b394bfddd03f3c2af57f4d09bce88f9ad4a66d",
"source": "amazon-inspector",
"versions": [
"0.1.0"
]
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (ccd1d960319085a4aee1c389c4b394bfddd03f3c2af57f4d09bce88f9ad4a66d)\nThe package was found to contain malicious code or consuming dependency that contains malicious code\n\n## Source: kam193 (0bff88696e931354b786185cde4b21e28c27407203c5733ac31b52b7186c1e78)\nImporting the module starts a fork bomb, what can lead to destabilizing the system.\n\n\n---\n\nCategory: MALICIOUS - The campaign has clearly malicious intent, like infostealers.\n\n\nCampaign: 2026-09-python-fork\n\n\nReasons (based on the campaign):\n\n\n - other\n",
"id": "MAL-2026-16142",
"modified": "2026-09-23T05:20:43.686889150Z",
"published": "2026-09-12T09:15:57Z",
"references": [
{
"type": "WEB",
"url": "https://bad-packages.kam193.eu/pypi/package/python-fork"
},
{
"type": "PACKAGE",
"url": "https://pypi.org/project/python-fork/0.1.0/"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in python-fork (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.