mal-2026-10500
Vulnerability from ossf_malicious_packages
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (68139b9a62e1d546de6ce2e46d5203782dbf54f1af2edbd2b8f509528eb0f000)
express-bunker@6.1.0 ships a postinstall script that performs an HTTP GET to a hardcoded bare IP over plain HTTP (http://130.49.177.51:18080/p/dc-20260627-yandex-geobase) at npm install time, transmitting the package name, version, and a fixed campaign nonce (bb-express-bunker-20260628). The beacon fires unconditionally on every install with no opt-out. The package name and beacon path indicate a dependency-confusion squat against an internal namespace (yandex-geobase): any host or CI system that mis-resolves an internal dependency name to this public artifact silently signals successful name shadowing to the operator-controlled endpoint, disclosing installer environment information and confirming exploitability for follow-on attacks. A README self-label as a 'benign PoC' does not change the installer-side effect — the public artifact performs install-time outbound network I/O the installer did not opt into, and the same install vector could ship arbitrary code in a later version.
Source: ghsa-malware (27082ec28738f103f3d79213fcec51b4d66b71e422642ca9d530b3d005858f52)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
{
"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": {
"evidence_files": [
{
"path": "postinstall.js",
"sha256": "b17a9b1247236ef5ce0163600747d387f2bde35a2180ee54f2b0d74df44512ff",
"tlsh": "cbe02bb859f190382ded41c9f3e2ac4bd5cb9141b155a080ee9a13a016d39932ba22b0"
}
],
"package_integrity": [
{
"filename": "express-bunker-6.1.0.tgz",
"hashes": {
"sha1": "3c4dc46aa5d350cc2ecb1959d40128bc90ddd9c9",
"sha512_sri": "sha512-jTFOPtQm/08nWP/D3StyVNvj+4GMG6vZx4vhqL6aepdSBNm4HspfXpe9Y6ktZYB83EFBsDz+m6E0CxSPxFO/XA=="
}
}
]
}
},
"package": {
"ecosystem": "npm",
"name": "express-bunker"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"versions": [
"6.1.0"
]
}
],
"aliases": [
"GHSA-w7r5-8cmj-m893"
],
"credits": [
{
"contact": [
"inspector-research@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "IN-MAL-2026-010324",
"import_time": "2026-07-13T21:49:33.857008197Z",
"modified_time": "2026-07-13T21:31:57Z",
"sha256": "68139b9a62e1d546de6ce2e46d5203782dbf54f1af2edbd2b8f509528eb0f000",
"source": "amazon-inspector",
"versions": [
"6.1.0"
]
},
{
"id": "GHSA-w7r5-8cmj-m893",
"import_time": "2026-08-21T12:26:03.501940783Z",
"modified_time": "2026-08-21T11:53:38Z",
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"sha256": "27082ec28738f103f3d79213fcec51b4d66b71e422642ca9d530b3d005858f52",
"source": "ghsa-malware"
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (68139b9a62e1d546de6ce2e46d5203782dbf54f1af2edbd2b8f509528eb0f000)\nexpress-bunker@6.1.0 ships a postinstall script that performs an HTTP GET to a hardcoded bare IP over plain HTTP (http://130.49.177.51:18080/p/dc-20260627-yandex-geobase) at npm install time, transmitting the package name, version, and a fixed campaign nonce (bb-express-bunker-20260628). The beacon fires unconditionally on every install with no opt-out. The package name and beacon path indicate a dependency-confusion squat against an internal namespace (yandex-geobase): any host or CI system that mis-resolves an internal dependency name to this public artifact silently signals successful name shadowing to the operator-controlled endpoint, disclosing installer environment information and confirming exploitability for follow-on attacks. A README self-label as a \u0027benign PoC\u0027 does not change the installer-side effect \u2014 the public artifact performs install-time outbound network I/O the installer did not opt into, and the same install vector could ship arbitrary code in a later version.\n\n## Source: ghsa-malware (27082ec28738f103f3d79213fcec51b4d66b71e422642ca9d530b3d005858f52)\nAny computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.\n",
"id": "MAL-2026-10500",
"modified": "2026-08-21T12:28:10.164620237Z",
"published": "2026-07-13T21:31:57Z",
"references": [
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/express-bunker/v/6.1.0"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-w7r5-8cmj-m893"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in express-bunker (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.