MAL-2026-17169
Vulnerability from ossf_malicious_packages
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (42d10ba1427af01794dfb0a6b39a05f969547455e9d86d75f18601b1d035c507)
preinstall.js runs unconditionally on npm install and POSTs a JSON payload to a hardcoded Pipedream collector at https://f5778d1d81cc30c39dcdd0da5ca1d49a.m.pipedream.net. The payload includes os.hostname(), os.userInfo() username, platform/arch/node version, process.env.INIT_CWD, process.cwd(), the consumer project's package.json name and version, whether the consumer declares an @alphaspace dependency, npm registry hosts parsed from ~/.npmrc, CI-related environment variable names, and proxy host configuration. The same script performs DNS resolution against a hardcoded list of .yahoo.com and .ouryahoo.com internal hostnames (including istio-system.prod1-gq1.omega.yahoo.com and buildr.corp.yahoo.com), and for any banana.stand.*.yahoo.com name that resolves it issues an https.request with rejectUnauthorized:false, capturing the response status, Server header, and first 512 bytes of the body and forwarding them in a banana_proof field of the exfil payload. The @alphaspace scope name and an in-file 'authorized security research' banner form a dependency-confusion lure aimed at Yahoo internal builds; the installer-side behavior — host fingerprinting, npmrc/registry disclosure, and TLS-verification-disabled internal-network probing from the installer's host — fires against any machine that resolves this package.
{
"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": "preinstall.js",
"sha256": "df9c95871cbcaed41914a65d50a746aee20b4a90becb0faf624018e87b3aff49",
"tlsh": "44815f3b85582d303ae0c57c6657114913a6f46b3e1466a4b28d324d6fccaee02b3abc"
}
],
"package_integrity": [
{
"filename": "core-99.0.0.tgz",
"hashes": {
"sha1": "558f50057e5ac0cb8f3de9a22b04b95c12943a4b",
"sha512_sri": "sha512-jm/lwDl6bVQybqhx+ZKboXVApqs9hrtFX8fVxrbdrpSFsWKNA2HxKOroN6z4bsLkj+LaBHjV200sFfYuH0NiTg=="
}
}
]
}
},
"package": {
"ecosystem": "npm",
"name": "@alphaspace/core"
},
"versions": [
"99.0.0",
"99.0.1",
"99.0.2"
]
}
],
"credits": [
{
"contact": [
"inspector-research@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "IN-MAL-2026-020551",
"import_time": "2026-09-25T02:45:29.111406131Z",
"modified_time": "2026-09-25T02:41:50Z",
"sha256": "0ab2a5d4024e6452d72efe9470634b7bf9fc3dbb0bd4d49d571138f777a81864",
"source": "amazon-inspector",
"versions": [
"99.0.0"
]
},
{
"id": "IN-MAL-2026-020550",
"import_time": "2026-09-25T02:45:29.08590051Z",
"modified_time": "2026-09-25T02:41:39Z",
"sha256": "0c7bcaf9dd8835f994b72bc50cf41ef1194429600fef3d271b99f32305ebd726",
"source": "amazon-inspector",
"versions": [
"99.0.1"
]
},
{
"id": "IN-MAL-2026-020543",
"import_time": "2026-09-25T02:45:28.888388754Z",
"modified_time": "2026-09-25T02:40:41Z",
"sha256": "42d10ba1427af01794dfb0a6b39a05f969547455e9d86d75f18601b1d035c507",
"source": "amazon-inspector",
"versions": [
"99.0.2"
]
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (42d10ba1427af01794dfb0a6b39a05f969547455e9d86d75f18601b1d035c507)\npreinstall.js runs unconditionally on npm install and POSTs a JSON payload to a hardcoded Pipedream collector at https://f5778d1d81cc30c39dcdd0da5ca1d49a.m.pipedream.net. The payload includes os.hostname(), os.userInfo() username, platform/arch/node version, process.env.INIT_CWD, process.cwd(), the consumer project\u0027s package.json name and version, whether the consumer declares an @alphaspace dependency, npm registry hosts parsed from ~/.npmrc, CI-related environment variable names, and proxy host configuration. The same script performs DNS resolution against a hardcoded list of *.yahoo.com and *.ouryahoo.com internal hostnames (including istio-system.prod1-gq1.omega.yahoo.com and buildr.corp.yahoo.com), and for any banana.stand.*.yahoo.com name that resolves it issues an https.request with rejectUnauthorized:false, capturing the response status, Server header, and first 512 bytes of the body and forwarding them in a banana_proof field of the exfil payload. The @alphaspace scope name and an in-file \u0027authorized security research\u0027 banner form a dependency-confusion lure aimed at Yahoo internal builds; the installer-side behavior \u2014 host fingerprinting, npmrc/registry disclosure, and TLS-verification-disabled internal-network probing from the installer\u0027s host \u2014 fires against any machine that resolves this package.\n",
"id": "MAL-2026-17169",
"modified": "2026-09-25T02:47:15Z",
"published": "2026-09-25T02:40:41Z",
"references": [
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/@alphaspace/core/v/99.0.0"
},
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/@alphaspace/core/v/99.0.1"
},
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/@alphaspace/core/v/99.0.2"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in @alphaspace/core (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.