MAL-2026-15812
Vulnerability from ossf_malicious_packages
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (2794273ee7e40da4b37c017636209acf1402b1104ab5fc265a43cc7d83228e72)
eslint-rxjs is a masquerade package whose npm metadata is internally inconsistent: the name references ESLint/RxJS, the description reads 'Integrate redis with cookies', and the author field impersonates well-known maintainers. The package ships no advertised functionality; index.cjs contains only a beacon helper. The package.json postinstall hook runs scripts/postinstall.cjs, which loads index.cjs and calls onInstall(), unconditionally issuing an HTTP GET to the hardcoded ngrok tunnel https://e493-95-216-46-122.ngrok-free.app/ping at install time. An ngrok-free.app subdomain is ephemeral, attacker-controlled infrastructure with no legitimate use for a published package; the request confirms code execution on the installer's machine and discloses the installer's source IP and install timing to that endpoint. This is the reconnaissance stage of a supply-chain dropper.
Source: ossf-package-analysis (994311f4267205d33ceb2b43d3f7d72767d384dcc286b6962b5cea13489f7280)
The OpenSSF Package Analysis project identified 'eslint-rxjs' @ 1.0.1 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
{
"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.cjs",
"sha256": "5d3e21578d1eefece343575bd3bd5f8bfbb88871e9e20f2618b8a826e66dca06",
"tlsh": "34e0d8991cbe22b58a71e3ba67171506ec92952b2fc0964673dcc5090f25a10c14ed0d"
},
{
"path": "package.json",
"sha256": "bee7d410a0f956fc962bfe1ace1339189b8e861e80112b87a344bd28de6b9ad9",
"tlsh": "e1f0d822ee148a2319f4866d48ac0102fb515b0f4034dc0f72ff2a1c07d227b589ab26"
}
],
"package_integrity": [
{
"filename": "eslint-rxjs-1.0.1.tgz",
"hashes": {
"sha1": "1f655d43e85199068e99c16ae7e2e713afb35050",
"sha512_sri": "sha512-WWXIVFmeHQVDUIZwNSQahJtmsMsXe4nvsvGhGi9dJd/p16KQTxXYLlumPuBCRjsl6BqgsjXZNXOHXIgjo0eh4A=="
}
}
]
}
},
"package": {
"ecosystem": "npm",
"name": "eslint-rxjs"
},
"versions": [
"1.0.1",
"1.0.0"
]
}
],
"credits": [
{
"contact": [
"inspector-research@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
},
{
"contact": [
"https://github.com/ossf/package-analysis",
"https://openssf.slack.com/channels/package_analysis"
],
"name": "OpenSSF: Package Analysis",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"import_time": "2026-09-02T02:44:29.209783706Z",
"modified_time": "2026-09-02T02:11:28Z",
"sha256": "994311f4267205d33ceb2b43d3f7d72767d384dcc286b6962b5cea13489f7280",
"source": "ossf-package-analysis",
"versions": [
"1.0.1"
]
},
{
"id": "IN-MAL-2026-019375",
"import_time": "2026-09-04T00:45:54.138897525Z",
"modified_time": "2026-09-03T23:48:37Z",
"sha256": "61a30ebdfe8d6fb82fe934cf8bc0327f06a336aebc2c73627286451e46c4b59b",
"source": "amazon-inspector",
"versions": [
"1.0.1"
]
},
{
"id": "IN-MAL-2026-019636",
"import_time": "2026-09-04T06:53:31.445132415Z",
"modified_time": "2026-09-04T06:37:03Z",
"sha256": "2794273ee7e40da4b37c017636209acf1402b1104ab5fc265a43cc7d83228e72",
"source": "amazon-inspector",
"versions": [
"1.0.0"
]
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (2794273ee7e40da4b37c017636209acf1402b1104ab5fc265a43cc7d83228e72)\neslint-rxjs is a masquerade package whose npm metadata is internally inconsistent: the name references ESLint/RxJS, the description reads \u0027Integrate redis with cookies\u0027, and the author field impersonates well-known maintainers. The package ships no advertised functionality; index.cjs contains only a beacon helper. The package.json postinstall hook runs scripts/postinstall.cjs, which loads index.cjs and calls onInstall(), unconditionally issuing an HTTP GET to the hardcoded ngrok tunnel https://e493-95-216-46-122.ngrok-free.app/ping at install time. An ngrok-free.app subdomain is ephemeral, attacker-controlled infrastructure with no legitimate use for a published package; the request confirms code execution on the installer\u0027s machine and discloses the installer\u0027s source IP and install timing to that endpoint. This is the reconnaissance stage of a supply-chain dropper.\n\n## Source: ossf-package-analysis (994311f4267205d33ceb2b43d3f7d72767d384dcc286b6962b5cea13489f7280)\nThe OpenSSF Package Analysis project identified \u0027eslint-rxjs\u0027 @ 1.0.1 (npm) as malicious.\n\nIt is considered malicious because:\n\n- The package communicates with a domain associated with malicious activity.\n",
"id": "MAL-2026-15812",
"modified": "2026-09-04T06:55:27.056987576Z",
"published": "2026-09-02T02:11:28Z",
"references": [
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/eslint-rxjs/v/1.0.1"
},
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/eslint-rxjs/v/1.0.0"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in eslint-rxjs (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.