mal-2026-16206
Vulnerability from ossf_malicious_packages
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (08299e41eb4feb9e324854bf5cd3386e6e52696b4b11443254374897a1ad3816)
index.js and the postinstall lifecycle script contact a hardcoded bare-IP endpoint at http://69.48.229.140:8080 over plain HTTP. On npm install, the postinstall hook collects host identifiers (hostname, username, platform, arch, cwd, node version, pid, all non-internal IP addresses, uptime, package name) and POSTs them as JSON to /b. On require() of the package main, the module beacons the same host, then polls /c every 30 seconds for JSON commands and executes the c field via child_process.exec, POSTing stdout/stderr back to /r. A source comment self-identifies the module as a stealth typosquat agent, while package.json advertises only a generic "small utility" description.
- CWE-506 - The product contains code that appears to be malicious in nature.
{
"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": "postinstall.js",
"sha256": "f96920db8aa0d72723e7eab7dc5319f4395a201f8eba307b4f81974730c1d75c",
"tlsh": "571165e00191a6293222a1f1ca5f150917e9e4101201fe98f83cd285bff4e7c07f69ec"
},
{
"path": "index.js",
"sha256": "a7fc4e3167420ca41e89f929a9721a63761e20c83b555338d91580d46e3dd3f1",
"tlsh": "ff4142eb91952124a17371f4ca5f64082bbad16202439e98bc2ce385af7493c072adfc"
}
],
"package_integrity": [
{
"filename": "pcomatch-1.0.0.tgz",
"hashes": {
"sha1": "1169c8d460a4cd79a384a0fdfe155ef5fc2f346e",
"sha512_sri": "sha512-p7NofNwT8UfpWnHQCH3C2appuPLy2YUEjcIy3Z4tNEJFXW438C+Gcf6h6Oigi7nfqm00a2Hv0Db55NNMkxaJGA=="
}
}
]
}
},
"package": {
"ecosystem": "npm",
"name": "@prime0/pcomatch"
},
"versions": [
"1.0.0"
]
}
],
"credits": [
{
"contact": [
"inspector-research@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "IN-MAL-2026-020073",
"import_time": "2026-09-16T06:31:14.494431104Z",
"modified_time": "2026-09-16T06:27:31Z",
"sha256": "08299e41eb4feb9e324854bf5cd3386e6e52696b4b11443254374897a1ad3816",
"source": "amazon-inspector",
"versions": [
"1.0.0"
]
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (08299e41eb4feb9e324854bf5cd3386e6e52696b4b11443254374897a1ad3816)\nindex.js and the postinstall lifecycle script contact a hardcoded bare-IP endpoint at http://69.48.229.140:8080 over plain HTTP. On `npm install`, the postinstall hook collects host identifiers (hostname, username, platform, arch, cwd, node version, pid, all non-internal IP addresses, uptime, package name) and POSTs them as JSON to /b. On `require()` of the package main, the module beacons the same host, then polls /c every 30 seconds for JSON commands and executes the `c` field via child_process.exec, POSTing stdout/stderr back to /r. A source comment self-identifies the module as a stealth typosquat agent, while package.json advertises only a generic \"small utility\" description.\n",
"id": "MAL-2026-16206",
"modified": "2026-09-16T06:27:31Z",
"published": "2026-09-16T06:27:31Z",
"references": [
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/@prime0/pcomatch/v/1.0.0"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in @prime0/pcomatch (npm)"
}
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.
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.