MAL-2026-16125
Vulnerability from ossf_malicious_packages – Published: 2026-09-10 20:14 – Updated: 2026-09-23 05:20 – Source website| Ecosystem | Package | Versions |
|---|---|---|
| PyPI |
lucy-python-script-2030
|
0.1.10.1.2
|
The package was found to contain malicious code or consuming dependency that contains malicious code
Starting version 0.1.1, the package contains an infostealer attempting to exfiltrate during import various sensitive data, like browser data, sensitive files, cloud credentials and others. In analyzed versions, the code contained mistakes effectievly disarming the functionality.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-09-lucy-python-script-2030
Reasons (based on the campaign):
-
infostealer
-
exfiltration-browser-data
-
files-exfiltration
-
persistence
-
The package contains code to detect if it is running in a sandbox environment.
-
uses-telegram-bot
-
exfiltration-cloud-tokens
No description from this source.
| Type | Indicator | Hashes |
|---|---|---|
| Package archive |
lucy_python_script_2030-0.1.1-py3-none-any.whl
|
blake2b_256
00b24cf70ec1c689a0d4a747e6c1c991a22adef36445cf67e3559f80669459f3md5
072e41180b774dcb24529f347e091770sha256
fb34aee91bb26d14bb74da23eca20b2212753d95fd22cd248f5d66af4189cdfa |
| Package archive |
lucy_python_script_2030-0.1.1.tar.gz
|
blake2b_256
eaced6676c21eda424cbc2651ee88f2713ece5f599d422bafbb0136f6447dfffmd5
2649b87ce315abc41e643b5f9520eebfsha256
b68bcf9401d928b8eceeb52a49bad08b03d2b4c57b11fa63269eee734eee46a5 |
- 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"
},
{
"cweId": "CWE-506",
"description": "The product contains code that appears to be malicious in nature.",
"name": "Embedded Malicious Code"
}
],
"indicators": {
"package_integrity": [
{
"filename": "lucy_python_script_2030-0.1.1-py3-none-any.whl",
"hashes": {
"blake2b_256": "00b24cf70ec1c689a0d4a747e6c1c991a22adef36445cf67e3559f80669459f3",
"md5": "072e41180b774dcb24529f347e091770",
"sha256": "fb34aee91bb26d14bb74da23eca20b2212753d95fd22cd248f5d66af4189cdfa"
}
},
{
"filename": "lucy_python_script_2030-0.1.1.tar.gz",
"hashes": {
"blake2b_256": "eaced6676c21eda424cbc2651ee88f2713ece5f599d422bafbb0136f6447dfff",
"md5": "2649b87ce315abc41e643b5f9520eebf",
"sha256": "b68bcf9401d928b8eceeb52a49bad08b03d2b4c57b11fa63269eee734eee46a5"
}
}
]
}
},
"package": {
"ecosystem": "PyPI",
"name": "lucy-python-script-2030"
},
"versions": [
"0.1.1",
"0.1.2"
]
}
],
"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-lucy-python-script-2030/lucy-python-script-2030",
"import_time": "2026-09-10T21:14:53.03593537Z",
"modified_time": "2026-09-10T20:14:14.693093Z",
"sha256": "0b93ebb2207ccfa0d02d068d444dce91835203dfe89a5ece38906158b4d3b891",
"source": "kam193",
"versions": [
"0.1.1",
"0.1.2"
]
},
{
"id": "IN-MAL-2026-020464",
"import_time": "2026-09-23T05:18:36.430164244Z",
"modified_time": "2026-09-23T05:11:01Z",
"sha256": "2195ea343abdb1205451fc7c778bdd1580cf985461949081852e9e82363ac389",
"source": "amazon-inspector",
"versions": [
"0.1.1"
]
},
{
"id": "IN-MAL-2026-020461",
"import_time": "2026-09-23T05:18:36.117260558Z",
"modified_time": "2026-09-23T05:10:33Z",
"sha256": "0c3e1aa299eb40840fbc9cfda67f2fab8f1302a3c0b53b119b36c8e851300fb9",
"source": "amazon-inspector",
"versions": [
"0.1.2"
]
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (2195ea343abdb1205451fc7c778bdd1580cf985461949081852e9e82363ac389)\nThe package was found to contain malicious code or consuming dependency that contains malicious code\n\n## Source: kam193 (0b93ebb2207ccfa0d02d068d444dce91835203dfe89a5ece38906158b4d3b891)\nStarting version 0.1.1, the package contains an infostealer attempting to exfiltrate during import various sensitive data, like browser data, sensitive files, cloud credentials and others. In analyzed versions, the code contained mistakes effectievly disarming the functionality.\n\n\n---\n\nCategory: MALICIOUS - The campaign has clearly malicious intent, like infostealers.\n\n\nCampaign: 2026-09-lucy-python-script-2030\n\n\nReasons (based on the campaign):\n\n\n - infostealer\n\n\n - exfiltration-browser-data\n\n\n - files-exfiltration\n\n\n - persistence\n\n\n - The package contains code to detect if it is running in a sandbox environment.\n\n\n - uses-telegram-bot\n\n\n - exfiltration-cloud-tokens\n",
"id": "MAL-2026-16125",
"modified": "2026-09-23T05:20:43.620427072Z",
"published": "2026-09-10T20:14:14Z",
"references": [
{
"type": "WEB",
"url": "https://bad-packages.kam193.eu/pypi/package/lucy-python-script-2030"
},
{
"type": "PACKAGE",
"url": "https://pypi.org/project/lucy-python-script-2030/0.1.1/"
},
{
"type": "PACKAGE",
"url": "https://pypi.org/project/lucy-python-script-2030/0.1.2/"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in lucy-python-script-2030 (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.