MAL-2026-15647
Vulnerability from ossf_malicious_packages
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (0b67d6f23451a756c154b86142f91615f5c08c415166c1f66216c8c83d74cbeb)
The package registers scripts/postinstall.cjs as an npm postinstall hook. Alongside a benign-looking config-writer, the script contains an obfuscation layer that uses a custom Fisher-Yates-style permutation (Dbv) to reconstruct the string 'constructor' from a scrambled seed, resolves it against a function object to obtain the Function constructor, decodes a scrambled payload body, and invokes Function('', )() at install time. Before invocation the wrapper stashes require, module, __dirname and __filename onto global under obfuscated keys so the decoded body can reach Node's module and filesystem APIs from within the Function() scope. The dist/ bundle additionally imports child_process and issues POST/GET calls from multiple files (dist/cli.cjs, dist/index.cjs, dist/service.cjs). No legitimate analytics/config bootstrap requires decoding an opaque scrambled string and executing it through Function.constructor, and the deliberate scope-escape scaffolding is characteristic of install-time droppers. The payload runs automatically on npm install on every installer machine.
Source: ghsa-malware (646f0dd17193e933882467e3c5e420f4d4e43611de485b52a33385b5aac13fda)
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": "scripts/postinstall.cjs",
"sha256": "79431c61c514f3ace7eb67389ffd9f84c7507de7f439318bf7b683babdc94910",
"tlsh": "70027d918acf5b2c06e2d14ae42e0327f873e5b63b9c9360b46cf0d55bd05112d7238a"
}
]
}
},
"package": {
"ecosystem": "npm",
"name": "@testrelic/appium-analytics"
},
"versions": [
"1.1.1-next.88"
]
}
],
"aliases": [
"GHSA-6cpr-jwvc-jhg7"
],
"credits": [
{
"contact": [
"inspector-research@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "GHSA-6cpr-jwvc-jhg7",
"import_time": "2026-08-31T19:20:45.977772055Z",
"modified_time": "2026-08-31T18:36:40Z",
"sha256": "646f0dd17193e933882467e3c5e420f4d4e43611de485b52a33385b5aac13fda",
"source": "ghsa-malware",
"versions": [
"1.1.1-next.88"
]
},
{
"id": "IN-MAL-2026-019389",
"import_time": "2026-09-04T00:45:55.058866288Z",
"modified_time": "2026-09-03T23:50:51Z",
"sha256": "0b67d6f23451a756c154b86142f91615f5c08c415166c1f66216c8c83d74cbeb",
"source": "amazon-inspector",
"versions": [
"1.1.1-next.88"
]
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (0b67d6f23451a756c154b86142f91615f5c08c415166c1f66216c8c83d74cbeb)\nThe package registers scripts/postinstall.cjs as an npm postinstall hook. Alongside a benign-looking config-writer, the script contains an obfuscation layer that uses a custom Fisher-Yates-style permutation (Dbv) to reconstruct the string \u0027constructor\u0027 from a scrambled seed, resolves it against a function object to obtain the Function constructor, decodes a scrambled payload body, and invokes Function(\u0027\u0027, \u003cdecoded\u003e)() at install time. Before invocation the wrapper stashes require, module, __dirname and __filename onto global under obfuscated keys so the decoded body can reach Node\u0027s module and filesystem APIs from within the Function() scope. The dist/ bundle additionally imports child_process and issues POST/GET calls from multiple files (dist/cli.cjs, dist/index.cjs, dist/service.cjs). No legitimate analytics/config bootstrap requires decoding an opaque scrambled string and executing it through Function.constructor, and the deliberate scope-escape scaffolding is characteristic of install-time droppers. The payload runs automatically on npm install on every installer machine.\n\n## Source: ghsa-malware (646f0dd17193e933882467e3c5e420f4d4e43611de485b52a33385b5aac13fda)\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-15647",
"modified": "2026-09-04T00:47:39.272076736Z",
"published": "2026-08-31T18:36:40Z",
"references": [
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-6cpr-jwvc-jhg7"
},
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/@testrelic/appium-analytics/v/1.1.1-next.88"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in @testrelic/appium-analytics (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.