MAL-2026-4556
Vulnerability from ossf_malicious_packages
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (f944bc544f9368e58a223e76e462ddec4ba325c728a233100182706ad8f0ae0e)
Package name mimics the legitimate express-enrouten route-discovery library, but the shipped index.js only hardcodes two demo routes rather than implementing automatic route discovery. The malicious mechanism is in package.json, which declares "node-fetch": "https://registry.ctzbg.com/express-enrouten-async/node-fetch" — a direct URL dependency pointing at a third-party, non-npm registry under a path namespaced to this package. On npm install, npm fetches and installs whatever tarball that URL serves as the installer's node-fetch, so any code requiring node-fetch in the host application loads attacker-controlled, unpinned, mutable bytes from a non-publisher domain. This is dependency-confusion-style supply-chain attack: the lookalike package name lures the install, and the URL-pinned fake node-fetch is the delivery vehicle for arbitrary code into the installer's dependency tree.
{
"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": {
"domains": [
"registry.ctzbg.com"
],
"evidence_files": [
{
"path": "package.json",
"sha256": "c651bc94ba9a5b86e3dafeed5a59bc0ced2646ab0c64296b451d65806e2a1b5d",
"tlsh": "811148b9cc245e130ec86762fcb91153ab528d0b4c49fc0a73ae61ac874d67b24bd46c"
},
{
"path": "index.js",
"sha256": "7b1a213f97b0828dfcda8477f93168b24c468ea22da945b2052bb8486943f685",
"tlsh": "e7f081bd3eb1074555e7f3cef262d0431811cb10a509da12a3dde3f00e815565a82da4"
}
],
"package_integrity": [
{
"filename": "express-enrouten-async-1.4.12.tgz",
"hashes": {
"sha1": "6898c06be298e67752380a9773d00994a717d4b0",
"sha512_sri": "sha512-PxA+Ou8SSZre8fsz5pbS4qOiIBXKOJt9J6Z9gikaLpmFgY9Xs684YaG7rnCChu5WABHi/uCkukbz2OGwaRoF+Q=="
}
}
]
}
},
"package": {
"ecosystem": "npm",
"name": "express-enrouten-async"
},
"versions": [
"1.4.12",
"1.4.11"
]
}
],
"credits": [
{
"contact": [
"actran@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "IN-MAL-2026-004244",
"import_time": "2026-05-26T05:52:13.476298611Z",
"modified_time": "2026-05-22T18:39:49Z",
"sha256": "5d8f74bd578bedcd5395600fd615f05122d59e27e0a59318ee226d123c67092c",
"source": "amazon-inspector",
"versions": [
"1.4.12"
]
},
{
"id": "IN-MAL-2026-004243",
"import_time": "2026-05-26T05:52:13.372950122Z",
"modified_time": "2026-05-22T18:39:48Z",
"sha256": "6ad6c1863bd00e262f6555b8e450c471e494e2f808c9f89ba09fa248689f8a24",
"source": "amazon-inspector",
"versions": [
"1.4.12"
]
},
{
"id": "IN-MAL-2026-004240",
"import_time": "2026-05-26T05:52:13.049225066Z",
"modified_time": "2026-05-22T18:36:43Z",
"sha256": "92452005ac9e56af97c1209041f118aa294e5a5350a6df1e943cea1fdb0e0b5b",
"source": "amazon-inspector",
"versions": [
"1.4.11"
]
},
{
"id": "IN-MAL-2026-004239",
"import_time": "2026-05-26T05:52:12.951657109Z",
"modified_time": "2026-05-22T18:36:43Z",
"sha256": "f944bc544f9368e58a223e76e462ddec4ba325c728a233100182706ad8f0ae0e",
"source": "amazon-inspector",
"versions": [
"1.4.11"
]
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (f944bc544f9368e58a223e76e462ddec4ba325c728a233100182706ad8f0ae0e)\nPackage name mimics the legitimate `express-enrouten` route-discovery library, but the shipped `index.js` only hardcodes two demo routes rather than implementing automatic route discovery. The malicious mechanism is in `package.json`, which declares `\"node-fetch\": \"https://registry.ctzbg.com/express-enrouten-async/node-fetch\"` \u2014 a direct URL dependency pointing at a third-party, non-npm registry under a path namespaced to this package. On `npm install`, npm fetches and installs whatever tarball that URL serves as the installer\u0027s `node-fetch`, so any code requiring `node-fetch` in the host application loads attacker-controlled, unpinned, mutable bytes from a non-publisher domain. This is dependency-confusion-style supply-chain attack: the lookalike package name lures the install, and the URL-pinned fake `node-fetch` is the delivery vehicle for arbitrary code into the installer\u0027s dependency tree.\n",
"id": "MAL-2026-4556",
"modified": "2026-05-26T05:55:02Z",
"published": "2026-05-22T18:36:43Z",
"references": [
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/express-enrouten-async/v/1.4.12"
},
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/express-enrouten-async/v/1.4.11"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in express-enrouten-async (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.