mal-2026-17761
Vulnerability from ossf_malicious_packages
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (042f083be94ae23751c73b5a73c0f11e4e9ecafd9ee9f1caa8c05b367ac71de8)
The package declares a postinstall script (postinstall.js) that runs automatically on npm install and collects a broad set of installer-side identifiers: hostname, username, uid/gid, home directory, platform, non-internal network interfaces with MAC addresses and CIDRs, configured DNS servers, internal reverse-DNS name, container runtime indicators, npm_* environment variables including the configured registry and scoped registry settings, CI marker variables, and the consuming project's package.json name, version, and declared dependency range for this package. The collected payload is POSTed as JSON to https://collector.oob.s4yhii.com/_npm-poc/beacon, and a DNS lookup beacon is issued against a subdomain of *.oob.s4yhii.com that encodes the package name as a label. The package is published under the @coopeuch scope at an implausibly high version 1.999.999 and specifically introspects the consumer manifest's declared dependency range and the installer's configured registry — a shape consistent with a dependency-confusion squat against an internal scope. Framing the behavior as a 'coordinated disclosure PoC' in author-controlled text does not change what the code does: installers that resolve this package in place of their internal @coopeuch/* package involuntarily disclose host, network, CI, and internal project metadata to a third-party endpoint.
- CWE-506 - The product contains code that appears to be malicious in nature.
{
"affected": [
{
"database_specific": {
"cwes": [
{
"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": "c859191e9d7e04d59b5d2f566799feb31594a68573350bd17661be469e8663ef",
"tlsh": "0ae1fa6a05fe1132226235f4694b50156776d1633504fbf4b9dd8280afcf0ba42bb7ed"
},
{
"path": "package.json",
"sha256": "f332f11dfad6a86ce4c8ecff5575cc421be92809f06fa0014c677060eeff3c3d",
"tlsh": "f9e09b30c5314f33a5d459a90d37654651d6285787183d1863e7426c4bdd77b88ff32d"
}
],
"package_integrity": [
{
"filename": "components-1.999.999.tgz",
"hashes": {
"sha1": "61fd6778893b8e0451cda30842609ab44aa0d4ad",
"sha512_sri": "sha512-ICou6OWE8bzhbyzDxcZ876+dt5El89qPEyYoKIbrNTqpIifnNuhmCxi3CFoeJxUyQOKKxoNYHLJ3NFkk/3IdFQ=="
}
}
]
}
},
"package": {
"ecosystem": "npm",
"name": "@coopeuch/components"
},
"versions": [
"1.999.999"
]
}
],
"credits": [
{
"contact": [
"inspector-research@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "IN-MAL-2026-021445",
"import_time": "2026-10-11T14:18:06.670881463Z",
"modified_time": "2026-10-11T14:00:55Z",
"sha256": "042f083be94ae23751c73b5a73c0f11e4e9ecafd9ee9f1caa8c05b367ac71de8",
"source": "amazon-inspector",
"versions": [
"1.999.999"
]
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (042f083be94ae23751c73b5a73c0f11e4e9ecafd9ee9f1caa8c05b367ac71de8)\nThe package declares a `postinstall` script (postinstall.js) that runs automatically on `npm install` and collects a broad set of installer-side identifiers: hostname, username, uid/gid, home directory, platform, non-internal network interfaces with MAC addresses and CIDRs, configured DNS servers, internal reverse-DNS name, container runtime indicators, `npm_*` environment variables including the configured registry and scoped registry settings, CI marker variables, and the consuming project\u0027s package.json name, version, and declared dependency range for this package. The collected payload is POSTed as JSON to `https://collector.oob.s4yhii.com/_npm-poc/beacon`, and a DNS lookup beacon is issued against a subdomain of `*.oob.s4yhii.com` that encodes the package name as a label. The package is published under the `@coopeuch` scope at an implausibly high version `1.999.999` and specifically introspects the consumer manifest\u0027s declared dependency range and the installer\u0027s configured registry \u2014 a shape consistent with a dependency-confusion squat against an internal scope. Framing the behavior as a \u0027coordinated disclosure PoC\u0027 in author-controlled text does not change what the code does: installers that resolve this package in place of their internal `@coopeuch/*` package involuntarily disclose host, network, CI, and internal project metadata to a third-party endpoint.\n",
"id": "MAL-2026-17761",
"modified": "2026-10-11T14:00:55Z",
"published": "2026-10-11T14:00:55Z",
"references": [
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/@coopeuch/components/v/1.999.999"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in @coopeuch/components (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.