mal-2026-17774
Vulnerability from ossf_malicious_packages
Published
2026-10-11 13:50
Modified
2026-10-11 14:19
Summary
Malicious code in nitro-bundled-dep (npm)
Details
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (0bbd4417bf91aba92399be259604511102ec5dfbacebe278a7922cf10c4deac5)
nitro-bundled-dep@99.0.1 ships a stub main module (a Proxy that no-ops any property access) plus beacon.cjs, which runs both from the postinstall lifecycle hook (node beacon.cjs) and on top-level require() of index.js. The beacon reads os.hostname(), __dirname (install path), process.cwd(), and process.version and POSTs them over plain HTTP to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc. The destination is not caller-configurable, is not associated with any published vendor, and has no relationship to the stated package purpose. The package name combined with version 99.0.1 and the inert stub body matches a dependency-confusion shape: an internal name resolved against the public registry at an implausibly high version pulls this beacon into the install, giving the operator of 185.158.107.175 confirmation of the host plus reconnaissance identifiers.
CWE
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"
}
],
"indicators": {
"evidence_files": [
{
"path": "beacon.cjs",
"sha256": "714abd13896833fdc6225b6cf615e48f4372fa51e5843cd3190a82b74ecfcce0",
"tlsh": "9d3161eba8f1a0489aaa7098c54f0409b17bf0078401af50fd6c83919f6193c33fa8dc"
},
{
"path": "index.js",
"sha256": "a86a4da763bbb34c16f361abe7aab66d5df591b66867ac8160041f932159b08d",
"tlsh": "2201d0d7225661b10b5221a4978f43c4a3b99d74027941d0d84a9226365108c463b8ee"
}
],
"package_integrity": [
{
"filename": "nitro-bundled-dep-99.0.1.tgz",
"hashes": {
"sha1": "b9251a9e983d4dbfc3b82d85a6745dc00cd4e98b",
"sha512_sri": "sha512-/rMcdKmg0buD3+b8YiOufdpoPIR/8L2PD/+8/5v7dK7RSVn3yhHIBeuUtpue2uw12T/JsLQK+r6/wRkCV7tryA=="
}
}
]
}
},
"package": {
"ecosystem": "npm",
"name": "nitro-bundled-dep"
},
"versions": [
"99.0.1",
"2.0.1",
"1.1.0"
]
}
],
"credits": [
{
"contact": [
"inspector-research@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "IN-MAL-2026-021380",
"import_time": "2026-10-11T14:18:00.905141556Z",
"modified_time": "2026-10-11T13:50:38Z",
"sha256": "0bbd4417bf91aba92399be259604511102ec5dfbacebe278a7922cf10c4deac5",
"source": "amazon-inspector",
"versions": [
"99.0.1"
]
},
{
"id": "IN-MAL-2026-021400",
"import_time": "2026-10-11T14:18:02.511535763Z",
"modified_time": "2026-10-11T13:53:42Z",
"sha256": "43f38c7ac6c0c53ea6787893d1a02c96e0a328e447c151104791f5b1ec4be0a3",
"source": "amazon-inspector",
"versions": [
"2.0.1"
]
},
{
"id": "IN-MAL-2026-021389",
"import_time": "2026-10-11T14:18:01.639057095Z",
"modified_time": "2026-10-11T13:52:07Z",
"sha256": "7291ba5dfedba6c562a9cf2641f3ec3f489d8d05721836f4fb2a1674ef4e808a",
"source": "amazon-inspector",
"versions": [
"1.1.0"
]
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (0bbd4417bf91aba92399be259604511102ec5dfbacebe278a7922cf10c4deac5)\nnitro-bundled-dep@99.0.1 ships a stub main module (a Proxy that no-ops any property access) plus beacon.cjs, which runs both from the postinstall lifecycle hook (`node beacon.cjs`) and on top-level require() of index.js. The beacon reads os.hostname(), __dirname (install path), process.cwd(), and process.version and POSTs them over plain HTTP to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc. The destination is not caller-configurable, is not associated with any published vendor, and has no relationship to the stated package purpose. The package name combined with version 99.0.1 and the inert stub body matches a dependency-confusion shape: an internal name resolved against the public registry at an implausibly high version pulls this beacon into the install, giving the operator of 185.158.107.175 confirmation of the host plus reconnaissance identifiers.\n",
"id": "MAL-2026-17774",
"modified": "2026-10-11T14:19:59Z",
"published": "2026-10-11T13:50:38Z",
"references": [
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/nitro-bundled-dep/v/99.0.1"
},
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/nitro-bundled-dep/v/2.0.1"
},
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/nitro-bundled-dep/v/1.1.0"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in nitro-bundled-dep (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…