mal-2026-17768
Vulnerability from ossf_malicious_packages
Published
2026-10-11 13:51
Modified
2026-10-11 17:17
Summary
Malicious code in cloudflare_module (npm)
Details
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (f3a545e1e930894c3320e68c2aee17dd2cec7f20ed03b2e882905056d0eee242)
Package cloudflare_module@99.0.1 is a dependency-confusion lure targeting the cloudflare_* namespace. package.json declares scripts.postinstall: "node beacon.cjs", and beacon.cjs POSTs a JSON payload containing os.hostname(), the install path (__dirname), process.cwd(), and process.version to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc over plain HTTP. The package main (index.js) additionally calls require('./beacon.cjs').fire() at top level inside a try/catch, so the same host-identifier POST also fires whenever a downstream bundler or application require()s the package. The default export is a Proxy that returns a no-op for every property access, allowing bundlers that resolve an internal cloudflare_module name to complete the build cleanly so the beacon callback fires without producing errors. The package is published at version 99.0.1 with a generic "Compatibility shim." description, consistent with version-bumping to beat an internal registry during resolution. The README self-labels the package as an "authorized dependency-confusion test," but the beacon targets any machine that resolves the name — the installer never consents to the exfiltration — and the destination is an unattributed bare-IP collector, not infrastructure of the targeted namespace.
CWE
- CWE-506 - The product contains code that appears to be malicious in nature.
- CWE-506 - The product contains code that appears to be malicious in nature.
- CWE-506 - The product contains code that appears to be malicious in nature.
- CWE-506 - The product contains code that appears to be malicious in nature.
Credits
{
"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"
},
{
"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": {
"evidence_files": [
{
"path": "beacon.cjs",
"sha256": "80779491720d41c53b5ed4cfbcbc70e9ebc144aaea61713d622eaa7a266c951b",
"tlsh": "813161eba8f0e048aaaa7098c54f0409b17af4078501af50f95d82915f6153c33fa8dc"
},
{
"path": "index.js",
"sha256": "a86a4da763bbb34c16f361abe7aab66d5df591b66867ac8160041f932159b08d",
"tlsh": "2201d0d7225661b10b5221a4978f43c4a3b99d74027941d0d84a9226365108c463b8ee"
}
],
"package_integrity": [
{
"filename": "cloudflare_module-3.0.0.tgz",
"hashes": {
"sha1": "11cb1eee1a57a04cd5f4c574706c16f470039730",
"sha512_sri": "sha512-+THmk0xaejcBalXPdQdXXIEXc4+a0hzFXshBDHPTkw72QTasmBzosaRPQEM9L4/cjIgyIwZcVjBFdOhEzEf0OQ=="
}
}
]
}
},
"package": {
"ecosystem": "npm",
"name": "cloudflare_module"
},
"versions": [
"3.0.0",
"1.0.1",
"1.0.0",
"99.0.1"
]
}
],
"credits": [
{
"contact": [
"inspector-research@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "IN-MAL-2026-021410",
"import_time": "2026-10-11T14:18:03.313936647Z",
"modified_time": "2026-10-11T13:55:13Z",
"sha256": "0aeadec01dbc6c39254740f8f4557d53f8d7ab94136a4695525a70cd3f80d95d",
"source": "amazon-inspector",
"versions": [
"3.0.0"
]
},
{
"id": "IN-MAL-2026-021387",
"import_time": "2026-10-11T14:18:01.469925982Z",
"modified_time": "2026-10-11T13:51:50Z",
"sha256": "14316e66f8d8eeb53b5fd4850537ac5398947feaf88f3837e39bfa587f60a0fb",
"source": "amazon-inspector",
"versions": [
"1.0.1"
]
},
{
"id": "IN-MAL-2026-021439",
"import_time": "2026-10-11T14:18:06.102897694Z",
"modified_time": "2026-10-11T13:59:51Z",
"sha256": "351579deaec7e5f856dfe103fbc8b7979b0f746e8e058bc3c1d35a00556bedf0",
"source": "amazon-inspector",
"versions": [
"1.0.0"
]
},
{
"id": "IN-MAL-2026-021448",
"import_time": "2026-10-11T17:15:51.556858866Z",
"modified_time": "2026-10-11T16:53:13Z",
"sha256": "f3a545e1e930894c3320e68c2aee17dd2cec7f20ed03b2e882905056d0eee242",
"source": "amazon-inspector",
"versions": [
"99.0.1"
]
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (f3a545e1e930894c3320e68c2aee17dd2cec7f20ed03b2e882905056d0eee242)\nPackage `cloudflare_module@99.0.1` is a dependency-confusion lure targeting the `cloudflare_*` namespace. `package.json` declares `scripts.postinstall: \"node beacon.cjs\"`, and `beacon.cjs` POSTs a JSON payload containing `os.hostname()`, the install path (`__dirname`), `process.cwd()`, and `process.version` to the hardcoded bare-IP endpoint `http://185.158.107.175:8787/_ah/dc` over plain HTTP. The package `main` (`index.js`) additionally calls `require(\u0027./beacon.cjs\u0027).fire()` at top level inside a try/catch, so the same host-identifier POST also fires whenever a downstream bundler or application `require()`s the package. The default export is a Proxy that returns a no-op for every property access, allowing bundlers that resolve an internal `cloudflare_module` name to complete the build cleanly so the beacon callback fires without producing errors. The package is published at version `99.0.1` with a generic \"Compatibility shim.\" description, consistent with version-bumping to beat an internal registry during resolution. The README self-labels the package as an \"authorized dependency-confusion test,\" but the beacon targets any machine that resolves the name \u2014 the installer never consents to the exfiltration \u2014 and the destination is an unattributed bare-IP collector, not infrastructure of the targeted namespace.\n",
"id": "MAL-2026-17768",
"modified": "2026-10-11T17:17:45.393219629Z",
"published": "2026-10-11T13:51:50Z",
"references": [
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/cloudflare_module/v/3.0.0"
},
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/cloudflare_module/v/1.0.1"
},
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/cloudflare_module/v/1.0.0"
},
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/cloudflare_module/v/99.0.1"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in cloudflare_module (npm)"
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
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.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
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.
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.
Loading…
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.
Loading…