mal-2026-15520
Vulnerability from ossf_malicious_packages
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (e3ea2aed3d7e8c0b9c99532d6714c486a5ad685418ebbd96c67b44b63f79fe01)
package.json declares a dependency whose key equals the package's own name (ring-device-settings-library) and whose value is a raw HTTPS URL pointing at an off-registry host: https://repo.securityctrl.com/ring-device-settings-library. On npm install, npm resolves that URL rather than a registry version range and installs whatever bytes the host returns, running any lifecycle scripts contained in the fetched artifact. There is no version pin, no integrity hash, and no signature check, and the host is unrelated to any npm registry. The shipped package contents are otherwise an inert placeholder, so the manifest line is the entire installed surface: whoever controls repo.securityctrl.com controls the code that executes on the installer's machine on every install. The self-referential dependency name, combined with the implausibly high version (45.0.0), is also a dependency-confusion shape that can win resolution against an internally-named package.
Source: ghsa-malware (fade0e594411cdfb0c5d2d1aa04eac0ff78edec368f574855613a92176f89d91)
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"
},
{
"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": "28fc31f840f9e9a4c3226959e8dbc36d87d6fc9905e1889708b8b7fa3dfa88c2",
"tlsh": "e4e0d8248e10123722de01569c78601773124f1f0234bc1adaea0029584e1b3a9f939c"
}
],
"package_integrity": [
{
"filename": "ring-device-settings-library-45.0.0.tgz",
"hashes": {
"sha1": "64108fb87882b81d4fadec23b475fbfad041de22",
"sha512_sri": "sha512-/ENN2H4D9KNY62NhlqDmiHkGZ4uJojHt9irJHmzrjiBInCBxDif3v0wtMwz/TZ80ndaAH9XHXHP7SEMI0VGvig=="
}
}
]
}
},
"package": {
"ecosystem": "npm",
"name": "ring-device-settings-library"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"versions": [
"45.0.0",
"30.0.0"
]
}
],
"aliases": [
"GHSA-f4f7-3wwr-hxfx",
"GHSA-c9hf-9c62-jcfq"
],
"credits": [
{
"contact": [
"inspector-research@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
},
{
"contact": [
"https://www.reversinglabs.com"
],
"name": "ReversingLabs",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "IN-MAL-2026-019085",
"import_time": "2026-08-28T23:14:37.257618411Z",
"modified_time": "2026-08-28T23:14:03Z",
"sha256": "e3ea2aed3d7e8c0b9c99532d6714c486a5ad685418ebbd96c67b44b63f79fe01",
"source": "amazon-inspector",
"versions": [
"45.0.0"
]
},
{
"id": "IN-MAL-2026-019108",
"import_time": "2026-08-28T23:38:06.193362536Z",
"modified_time": "2026-08-28T23:17:23Z",
"sha256": "1e720186a5ba3e3a2e12f670a2b9d9b080b5cc4cfcd1098bd42e25db9327d803",
"source": "amazon-inspector",
"versions": [
"30.0.0"
]
},
{
"id": "GHSA-f4f7-3wwr-hxfx",
"import_time": "2026-08-29T18:26:29.959327099Z",
"modified_time": "2026-08-29T18:13:37Z",
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"sha256": "fade0e594411cdfb0c5d2d1aa04eac0ff78edec368f574855613a92176f89d91",
"source": "ghsa-malware"
},
{
"id": "RLMA-2026-10781",
"import_time": "2026-09-24T09:21:35.391435852Z",
"modified_time": "2026-09-22T17:39:04Z",
"sha256": "46882c4e34d999ec66db5cd4a3096cb252253d5e74b0087c0593414aba75de02",
"source": "reversing-labs",
"versions": [
"45.0.0"
]
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (e3ea2aed3d7e8c0b9c99532d6714c486a5ad685418ebbd96c67b44b63f79fe01)\npackage.json declares a dependency whose key equals the package\u0027s own name (ring-device-settings-library) and whose value is a raw HTTPS URL pointing at an off-registry host: https://repo.securityctrl.com/ring-device-settings-library. On `npm install`, npm resolves that URL rather than a registry version range and installs whatever bytes the host returns, running any lifecycle scripts contained in the fetched artifact. There is no version pin, no integrity hash, and no signature check, and the host is unrelated to any npm registry. The shipped package contents are otherwise an inert placeholder, so the manifest line is the entire installed surface: whoever controls repo.securityctrl.com controls the code that executes on the installer\u0027s machine on every install. The self-referential dependency name, combined with the implausibly high version (45.0.0), is also a dependency-confusion shape that can win resolution against an internally-named package.\n\n## Source: ghsa-malware (fade0e594411cdfb0c5d2d1aa04eac0ff78edec368f574855613a92176f89d91)\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-15520",
"modified": "2026-09-24T09:23:28.564060057Z",
"published": "2026-08-28T23:14:03Z",
"references": [
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/ring-device-settings-library/v/45.0.0"
},
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/ring-device-settings-library/v/30.0.0"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-f4f7-3wwr-hxfx"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-c9hf-9c62-jcfq"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in ring-device-settings-library (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.