mal-2026-15866
Vulnerability from ossf_malicious_packages
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (a80fea2ddf5689952ca33aee5f32efb088024bd1a243621b558d3cdc41ed7d57)
package.json at line 14 declares a runtime dependency microfrontend whose source is a bare HTTPS URL (https://repo.artifactorymanager.com/bx-ui-framework/authentication) rather than an npm registry version range. On npm install, npm fetches whatever bytes that host returns and installs them as a dependency, running any lifecycle scripts contained in the fetched artifact. There is no version pin, no integrity hash, and no signature check, so the delivered content is fully controlled by whoever operates repo.artifactorymanager.com, and can change between installs. The shipped package itself is a minimal stub, so this manifest entry is effectively the entire installable payload. The dependency key (microfrontend) does not match the package's own name, and the host domain is unrelated to any npm-scope publisher identity for @bx-ui-framework.
{
"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"
},
{
"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": "f3871037c4fe6b2a224e5f9f3a5885df395ee694c9c1d127505466c965f1d29b",
"tlsh": "b4e0a31645b00cb757c603f2e925014237e24f1f79487c094687691c429d5f658f93cd"
}
],
"package_integrity": [
{
"filename": "authentication-1.2.0.tgz",
"hashes": {
"sha1": "6cf186317b4d5bb3b9fdee43b0f2c2175170fdf8",
"sha512_sri": "sha512-xPo7U/DZmiQCHyfyLIn91lnPXxzlXEkIH+AJRJSxc0yoOm1VXt0xK3AnTNbYsHuiUvOKS+45WIOgc+gAlpsUnQ=="
}
}
]
}
},
"package": {
"ecosystem": "npm",
"name": "@bx-ui-framework/authentication"
},
"versions": [
"1.2.0",
"15.0.0",
"16.0.0"
]
}
],
"credits": [
{
"contact": [
"inspector-research@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "IN-MAL-2026-019406",
"import_time": "2026-09-04T01:24:41.399774573Z",
"modified_time": "2026-09-04T01:12:31Z",
"sha256": "8562942e7b9d79df895b98cbb49f25b83ee812cacd25b48a48eb81c619bbbfaf",
"source": "amazon-inspector",
"versions": [
"1.2.0"
]
},
{
"id": "IN-MAL-2026-019405",
"import_time": "2026-09-04T01:24:41.327272508Z",
"modified_time": "2026-09-04T01:12:20Z",
"sha256": "a80fea2ddf5689952ca33aee5f32efb088024bd1a243621b558d3cdc41ed7d57",
"source": "amazon-inspector",
"versions": [
"15.0.0"
]
},
{
"id": "IN-MAL-2026-019646",
"import_time": "2026-09-04T21:15:21.007109864Z",
"modified_time": "2026-09-04T21:04:48Z",
"sha256": "42f0972647de2c53dd2af11def327f594a17d62c5425b63c74a46305556d60dd",
"source": "amazon-inspector",
"versions": [
"16.0.0"
]
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (a80fea2ddf5689952ca33aee5f32efb088024bd1a243621b558d3cdc41ed7d57)\npackage.json at line 14 declares a runtime dependency `microfrontend` whose source is a bare HTTPS URL (`https://repo.artifactorymanager.com/bx-ui-framework/authentication`) rather than an npm registry version range. On `npm install`, npm fetches whatever bytes that host returns and installs them as a dependency, running any lifecycle scripts contained in the fetched artifact. There is no version pin, no integrity hash, and no signature check, so the delivered content is fully controlled by whoever operates `repo.artifactorymanager.com`, and can change between installs. The shipped package itself is a minimal stub, so this manifest entry is effectively the entire installable payload. The dependency key (`microfrontend`) does not match the package\u0027s own name, and the host domain is unrelated to any npm-scope publisher identity for `@bx-ui-framework`.\n",
"id": "MAL-2026-15866",
"modified": "2026-09-04T21:17:04.806790821Z",
"published": "2026-09-04T01:12:20Z",
"references": [
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/@bx-ui-framework/authentication/v/1.2.0"
},
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/@bx-ui-framework/authentication/v/15.0.0"
},
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/@bx-ui-framework/authentication/v/16.0.0"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in @bx-ui-framework/authentication (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.