mal-2026-15526
Vulnerability from ossf_malicious_packages
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (b8893c0594fed4d622c0e347b4e8f899d5b00e11c15fe31e09169a9fae8e82be)
package.json at line 11 declares a dependency whose key equals this package's own name (analytics-web-client) and whose source is a bare HTTPS URL (https://repo.securityctrl.com/analytics-web-client) rather than a registry version range. On npm install, npm fetches whatever bytes that host serves and runs any lifecycle scripts they contain, with no version pin and no integrity check. The shipped index.js is an inert stub, so the manifest line is the entire published surface: whoever controls repo.securityctrl.com controls code executed on the installer's machine at install time. The self-referential dependency name additionally matches the dependency-confusion shape, aimed at winning resolution against an internal package of the same name.
Source: ghsa-malware (8d97301c6daf1b647ec2c8159dd37cbd58af229893bda8fac5475346e71c93b7)
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": "b048b5946292ad96364ca63c637cfd2fbd2837edbaf75363da66885c644ff021",
"tlsh": "23e0d6209922233721c6639388be8893f3344f1b2044bc0ad68a481c864f1b369fa2ad"
}
],
"package_integrity": [
{
"filename": "analytics-web-client-30.0.0.tgz",
"hashes": {
"sha1": "f4164476ae684c253c20cda9a82e7e190eef2c63",
"sha512_sri": "sha512-4Rj/zq7xlNznAAzJLqnDwvVPvOiCfV3i+tDZoMlwD9gqPDJQSALhe/4JYPdaHre/efngnn4uxrQ5d/rAuO1rcQ=="
}
}
]
}
},
"package": {
"ecosystem": "npm",
"name": "analytics-web-client"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"versions": [
"30.0.0"
]
}
],
"aliases": [
"GHSA-5g5q-647h-8vv8"
],
"credits": [
{
"contact": [
"inspector-research@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "IN-MAL-2026-019110",
"import_time": "2026-08-28T23:38:06.387039522Z",
"modified_time": "2026-08-28T23:17:38Z",
"sha256": "b8893c0594fed4d622c0e347b4e8f899d5b00e11c15fe31e09169a9fae8e82be",
"source": "amazon-inspector",
"versions": [
"30.0.0"
]
},
{
"id": "GHSA-5g5q-647h-8vv8",
"import_time": "2026-08-29T18:26:29.94500139Z",
"modified_time": "2026-08-29T18:13:37Z",
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"sha256": "8d97301c6daf1b647ec2c8159dd37cbd58af229893bda8fac5475346e71c93b7",
"source": "ghsa-malware"
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (b8893c0594fed4d622c0e347b4e8f899d5b00e11c15fe31e09169a9fae8e82be)\npackage.json at line 11 declares a dependency whose key equals this package\u0027s own name (analytics-web-client) and whose source is a bare HTTPS URL (https://repo.securityctrl.com/analytics-web-client) rather than a registry version range. On npm install, npm fetches whatever bytes that host serves and runs any lifecycle scripts they contain, with no version pin and no integrity check. The shipped index.js is an inert stub, so the manifest line is the entire published surface: whoever controls repo.securityctrl.com controls code executed on the installer\u0027s machine at install time. The self-referential dependency name additionally matches the dependency-confusion shape, aimed at winning resolution against an internal package of the same name.\n\n## Source: ghsa-malware (8d97301c6daf1b647ec2c8159dd37cbd58af229893bda8fac5475346e71c93b7)\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-15526",
"modified": "2026-08-29T18:28:20.396997652Z",
"published": "2026-08-28T23:17:38Z",
"references": [
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/analytics-web-client/v/30.0.0"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-5g5q-647h-8vv8"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in analytics-web-client (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.