MAL-2026-18752
Vulnerability from ossf_malicious_packages – Published: 2026-11-07 10:16 – Updated: 2026-11-10 09:15 – Source website| Ecosystem | Package | Versions |
|---|---|---|
| PyPI |
qzc690384
|
1.0.0
|
The adjudication model's output was cut off by the provider safety filter on every attempt, which happens when the reviewed code reads like operational malware. Scores come from the partial verdict when it carried them; confidence is capped so a person reviews this version before any block.
In this campaign, packages execute malicious code during installation. The exact behavior varies between versions: fingerprinting environment, exposing a backdoor server listening for remote commands, downloading remote commands from a hardcoded location. Next stages seem to be downloaded from localhost, what suggests the code may still be a preparation for the real attack.
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2026-11-qzc
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 contains code to execute remote commands (probably limited to a specific set) on the victim's machine.
-
backdoor
-
The package overrides the install command in setup.py to execute malicious code during installation.
The OpenSSF Package Analysis project identified 'qzc690384' @ 1.0.0 (pypi) as malicious.
It is considered malicious because:
- The package executes one or more commands associated with malicious behavior.
| Type | Indicator | Hashes |
|---|---|---|
| Evidence file |
setup.py
|
sha256
1f15ebe658be788e2703452efbd48e481b78c7172cc0dfd858a1b54d4cedb92atlsh
c3317646d47619a3f38794a81c96c43177599f1f8a11ac20badc077c2fc8478e3b25e6 |
| Package archive |
qzc690384-1.0.0.tar.gz
|
blake2b_256
e08ef4ce92b3212f13d7095aca350414faebf0755afc2429d5e50b14883b48a7md5
b1d50ccb3886f014c116ee5ca30d157asha256
d91c95ed56f51987aaa7e8ad2c8fc68bf639b391c609a4c719a544ec0d49bd3e |
- 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": [
{
"artifacts": [
"qzc690384-1.0.0.tar.gz"
],
"path": "setup.py",
"sha256": "1f15ebe658be788e2703452efbd48e481b78c7172cc0dfd858a1b54d4cedb92a",
"tlsh": "c3317646d47619a3f38794a81c96c43177599f1f8a11ac20badc077c2fc8478e3b25e6"
}
],
"package_integrity": [
{
"filename": "qzc690384-1.0.0.tar.gz",
"hashes": {
"blake2b_256": "e08ef4ce92b3212f13d7095aca350414faebf0755afc2429d5e50b14883b48a7",
"md5": "b1d50ccb3886f014c116ee5ca30d157a",
"sha256": "d91c95ed56f51987aaa7e8ad2c8fc68bf639b391c609a4c719a544ec0d49bd3e"
}
}
]
}
},
"package": {
"ecosystem": "PyPI",
"name": "qzc690384"
},
"versions": [
"1.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"
},
{
"contact": [
"https://github.com/ossf/package-analysis",
"https://openssf.slack.com/channels/package_analysis"
],
"name": "OpenSSF: Package Analysis",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "pypi/2026-11-qzc/qzc690384",
"import_time": "2026-11-07T15:10:15.551805171Z",
"modified_time": "2026-11-07T14:41:21.430164Z",
"sha256": "dbd73fb476a20a6d0f4bc4fe820a007283789e6c03548f93e67fff7a58b2ede1",
"source": "kam193",
"versions": [
"1.0.0"
]
},
{
"id": "IN-MAL-2026-022556",
"import_time": "2026-11-07T20:36:36.874744019Z",
"modified_time": "2026-11-07T20:17:54Z",
"sha256": "2aaf64364e0f3a5688772d501b9400cd9caf65ecdc82a869844ff73999aff2e4",
"source": "amazon-inspector",
"versions": [
"1.0.0"
]
},
{
"import_time": "2026-11-10T09:13:11.870963119Z",
"modified_time": "2026-11-07T10:16:07Z",
"sha256": "7e9e91aa206dd7ddf45ac0fe78218c4e247de029fb70f74e2fc1a30959f6d4c8",
"source": "ossf-package-analysis",
"versions": [
"1.0.0"
]
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (2aaf64364e0f3a5688772d501b9400cd9caf65ecdc82a869844ff73999aff2e4)\nThe adjudication model\u0027s output was cut off by the provider safety filter on every attempt, which happens when the reviewed code reads like operational malware. Scores come from the partial verdict when it carried them; confidence is capped so a person reviews this version before any block.\n\n## Source: kam193 (dbd73fb476a20a6d0f4bc4fe820a007283789e6c03548f93e67fff7a58b2ede1)\nIn this campaign, packages execute malicious code during installation. The exact behavior varies between versions: fingerprinting environment, exposing a backdoor server listening for remote commands, downloading remote commands from a hardcoded location. Next stages seem to be downloaded from localhost, what suggests the code may still be a preparation for the real attack.\n\n\n---\n\nCategory: MALICIOUS - The campaign has clearly malicious intent, like infostealers.\n\n\nCampaign: 2026-11-qzc\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 contains code to execute remote commands (probably limited to a specific set) on the victim\u0027s machine.\n\n\n - backdoor\n\n\n - The package overrides the install command in setup.py to execute malicious code during installation.\n\n## Source: ossf-package-analysis (7e9e91aa206dd7ddf45ac0fe78218c4e247de029fb70f74e2fc1a30959f6d4c8)\nThe OpenSSF Package Analysis project identified \u0027qzc690384\u0027 @ 1.0.0 (pypi) as malicious.\n\nIt is considered malicious because:\n\n- The package executes one or more commands associated with malicious behavior.\n",
"id": "MAL-2026-18752",
"modified": "2026-11-10T09:15:00.369802519Z",
"published": "2026-11-07T10:16:07Z",
"references": [
{
"type": "WEB",
"url": "https://bad-packages.kam193.eu/pypi/package/qzc690384"
},
{
"type": "PACKAGE",
"url": "https://pypi.org/project/qzc690384/1.0.0/"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in qzc690384 (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.