mal-2026-17760
Vulnerability from ossf_malicious_packages
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (887c41c0805d7d223c499e702796cf46727b0be152b7c8a65607907afb3b5d59)
@coopeuch/common@1.999.999 publishes to the public npm registry under a scope the publisher does not own, using an inflated version (1.999.999) consistent with the dependency-confusion technique that outranks internal-registry versions. The package's declared postinstall script (postinstall.js) runs automatically on npm install and collects installer-side host and network data — hostname, username, uid/gid, home directory, non-internal network interface addresses with MAC/CIDR, DNS resolver addresses, reverse-DNS internal FQDN, container markers, CI environment-variable presence, npm_config_registry, and the consuming project's package name/version/declared range — then POSTs it as JSON to the hardcoded author-controlled endpoint https://collector.oob.s4yhii.com/_npm-poc/beacon. A secondary DNS beacon is emitted via dns.lookup to a subdomain of oob.s4yhii.com. Any build that resolves @coopeuch/common from the public registry (including internal builds referencing the @coopeuch scope) will auto-exfiltrate internal hostnames, MAC addresses, usernames, internal registry URLs, and project identity to a third-party collector at install time. The package's README self-labels this as a coordinated-disclosure proof of concept; the harvesting and off-host upload nonetheless occur without installer opt-in.
- 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": "0460202496c4e21d871ff51598019aeb1d27b5083ebf22611dc5456a64d0dbaa",
"tlsh": "1ee02230c5314f33a4d829a90d37264660aa296387083c2863eb426c4bdc77b88ff32d"
}
],
"package_integrity": [
{
"filename": "common-1.999.999.tgz",
"hashes": {
"sha1": "f1278ee12b8adc385a28b5847ebbaef5f4e41be7",
"sha512_sri": "sha512-aVYGJ0N6KMZH6QKeZwlw88VVV1+9Nh1lLGmbI/R7fCWJvnLnoiBRe7op2ptvfDIokoyiyPKyCuvJmvfs33mT0Q=="
}
}
]
}
},
"package": {
"ecosystem": "npm",
"name": "@coopeuch/common"
},
"versions": [
"1.999.999"
]
}
],
"credits": [
{
"contact": [
"inspector-research@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "IN-MAL-2026-021433",
"import_time": "2026-10-11T14:18:05.240602486Z",
"modified_time": "2026-10-11T13:58:48Z",
"sha256": "887c41c0805d7d223c499e702796cf46727b0be152b7c8a65607907afb3b5d59",
"source": "amazon-inspector",
"versions": [
"1.999.999"
]
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (887c41c0805d7d223c499e702796cf46727b0be152b7c8a65607907afb3b5d59)\n@coopeuch/common@1.999.999 publishes to the public npm registry under a scope the publisher does not own, using an inflated version (1.999.999) consistent with the dependency-confusion technique that outranks internal-registry versions. The package\u0027s declared postinstall script (postinstall.js) runs automatically on npm install and collects installer-side host and network data \u2014 hostname, username, uid/gid, home directory, non-internal network interface addresses with MAC/CIDR, DNS resolver addresses, reverse-DNS internal FQDN, container markers, CI environment-variable presence, npm_config_registry, and the consuming project\u0027s package name/version/declared range \u2014 then POSTs it as JSON to the hardcoded author-controlled endpoint https://collector.oob.s4yhii.com/_npm-poc/beacon. A secondary DNS beacon is emitted via dns.lookup to a subdomain of oob.s4yhii.com. Any build that resolves @coopeuch/common from the public registry (including internal builds referencing the @coopeuch scope) will auto-exfiltrate internal hostnames, MAC addresses, usernames, internal registry URLs, and project identity to a third-party collector at install time. The package\u0027s README self-labels this as a coordinated-disclosure proof of concept; the harvesting and off-host upload nonetheless occur without installer opt-in.\n",
"id": "MAL-2026-17760",
"modified": "2026-10-11T13:58:48Z",
"published": "2026-10-11T13:58:48Z",
"references": [
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/@coopeuch/common/v/1.999.999"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in @coopeuch/common (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.