mal-2026-16440
Vulnerability from ossf_malicious_packages
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (a25d8c29cbfb317e1c88568514a999618bdeee25b2716b76e3db5062e9dd7a67)
package.json at line 43 declares the sole dependency 'node-net-pool' as an HTTPS tarball of the 'main' branch of an unrelated GitHub account (https://github.com/trktgq0wbre1/node-net-pool/archive/refs/heads/main.tar.gz), not a registry version range. npm install fetches whatever bytes that URL currently serves, unpinned and with no integrity check, and runs any lifecycle scripts inside it; the package's postinstall then require()s node-net-pool so its top-level code executes on the installer's machine. The dependency source is under an account unrelated to the declared repository turbo-ws-dev/turbo-ws, and the package's own description advertises 'zero dependencies', contradicting the manifest. Whoever controls the referenced GitHub account controls code executed on every installer of turbo-ws.
Source: ghsa-malware (71a94f67778999b9ca3320ab83c7c2df9958d169c79b35fc7e2d03eb99b4e776)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
{
"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": "package.json",
"sha256": "7f84ab7675f41e8f3c5dcaac3b100d6c4b427050928faa07470c2880047ad50d",
"tlsh": "2031ea2ac9b899bb35c511e4e8195113f66208234998bd00b3c341fc4fce5db91ff5ad"
}
],
"package_integrity": [
{
"filename": "turbo-ws-1.0.0.tgz",
"hashes": {
"sha1": "f00fff966b59f22fa0ff25b60b1243e1dc8a5bc8",
"sha512_sri": "sha512-KQ+nijvvuiPSjc9683PuqAC1/FMUgUFvuf7EIi+0al8GW6mpd5wcpC1Z7kUiab0VsXtSqMmMOTxrWTEwVVBu8g=="
}
}
]
}
},
"package": {
"ecosystem": "npm",
"name": "turbo-ws"
},
"versions": [
"1.0.0"
]
}
],
"aliases": [
"GHSA-3933-m2c5-xfm8"
],
"credits": [
{
"contact": [
"inspector-research@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "IN-MAL-2026-020333",
"import_time": "2026-09-23T02:26:00.41189189Z",
"modified_time": "2026-09-23T01:58:25Z",
"sha256": "a25d8c29cbfb317e1c88568514a999618bdeee25b2716b76e3db5062e9dd7a67",
"source": "amazon-inspector",
"versions": [
"1.0.0"
]
},
{
"id": "GHSA-3933-m2c5-xfm8",
"import_time": "2026-10-02T23:23:00.335386487Z",
"modified_time": "2026-10-02T22:31:51Z",
"sha256": "71a94f67778999b9ca3320ab83c7c2df9958d169c79b35fc7e2d03eb99b4e776",
"source": "ghsa-malware",
"versions": [
"1.0.0"
]
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (a25d8c29cbfb317e1c88568514a999618bdeee25b2716b76e3db5062e9dd7a67)\npackage.json at line 43 declares the sole dependency \u0027node-net-pool\u0027 as an HTTPS tarball of the \u0027main\u0027 branch of an unrelated GitHub account (https://github.com/trktgq0wbre1/node-net-pool/archive/refs/heads/main.tar.gz), not a registry version range. npm install fetches whatever bytes that URL currently serves, unpinned and with no integrity check, and runs any lifecycle scripts inside it; the package\u0027s postinstall then require()s node-net-pool so its top-level code executes on the installer\u0027s machine. The dependency source is under an account unrelated to the declared repository turbo-ws-dev/turbo-ws, and the package\u0027s own description advertises \u0027zero dependencies\u0027, contradicting the manifest. Whoever controls the referenced GitHub account controls code executed on every installer of turbo-ws.\n\n## Source: ghsa-malware (71a94f67778999b9ca3320ab83c7c2df9958d169c79b35fc7e2d03eb99b4e776)\nAny computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.\n",
"id": "MAL-2026-16440",
"modified": "2026-10-02T23:24:40.474292895Z",
"published": "2026-09-23T01:58:25Z",
"references": [
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/turbo-ws/v/1.0.0"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-3933-m2c5-xfm8"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in turbo-ws (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.