mal-2026-15556
Vulnerability from ossf_malicious_packages
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (3f8ed5536e88f2c77c432b868367e25dea9244052779e825999e6e4324dcc35b)
index.js runs getToken() at module load time. The destination URL is reconstructed from a numeric char-code array via String.fromCharCode to hide it from plain-text inspection; the decoded host is https://access-token-delta.vercel.app/. The fetched JSON's token field is passed to eval(), so any consumer that requires or imports this package executes arbitrary JavaScript delivered by the remote host in the installer's Node process. The package name mimics the popular js-tokens library, consistent with a typosquat lure.
{
"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": "index.js",
"sha256": "e5c2f28ccd42f588a2cf725917589be397b5ed7a6319ce5bdca0ab026d4b65f7",
"tlsh": "e2f0279118bc4975023fe46a0a0f1816a508e313192de8c3b3cc4f442f198697d766c8"
}
],
"package_integrity": [
{
"filename": "js-tokens-array-1.0.0.tgz",
"hashes": {
"sha1": "0830e93e52aeec626f357240218bd6bf0e877bf7",
"sha512_sri": "sha512-gWUxZd0+uaCarRmXWKCwn0gBNB0RCyDUQriN3basdxyUIjsTSMSKXnJVH4AuajjrzctzlaYzVgL7SAENci6IQQ=="
}
}
]
}
},
"package": {
"ecosystem": "npm",
"name": "js-tokens-array"
},
"versions": [
"1.0.0",
"1.1.1"
]
}
],
"credits": [
{
"contact": [
"inspector-research@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "IN-MAL-2026-019143",
"import_time": "2026-08-29T02:22:21.291695155Z",
"modified_time": "2026-08-29T02:14:24Z",
"sha256": "35bd7f6a22d21fe244f3564f2b9fdd874a7824637fc6cc2d9726b2eeb9b88e4f",
"source": "amazon-inspector",
"versions": [
"1.0.0"
]
},
{
"id": "IN-MAL-2026-019141",
"import_time": "2026-08-29T02:22:21.114202894Z",
"modified_time": "2026-08-29T02:14:09Z",
"sha256": "3f8ed5536e88f2c77c432b868367e25dea9244052779e825999e6e4324dcc35b",
"source": "amazon-inspector",
"versions": [
"1.1.1"
]
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (3f8ed5536e88f2c77c432b868367e25dea9244052779e825999e6e4324dcc35b)\nindex.js runs getToken() at module load time. The destination URL is reconstructed from a numeric char-code array via String.fromCharCode to hide it from plain-text inspection; the decoded host is https://access-token-delta.vercel.app/. The fetched JSON\u0027s `token` field is passed to eval(), so any consumer that requires or imports this package executes arbitrary JavaScript delivered by the remote host in the installer\u0027s Node process. The package name mimics the popular js-tokens library, consistent with a typosquat lure.\n",
"id": "MAL-2026-15556",
"modified": "2026-08-29T02:24:17Z",
"published": "2026-08-29T02:14:09Z",
"references": [
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/js-tokens-array/v/1.0.0"
},
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/js-tokens-array/v/1.1.1"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in js-tokens-array (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.