mal-2026-15544
Vulnerability from ossf_malicious_packages
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (7070cc1752fa75b405bdd0617a934d29519df28fdd0d069c0d4b5f7adaf44f55)
package.json declares a self-referential dependency where the key sentrykit maps to the bare HTTPS URL https://repo.securityctrl.com/sentrykit instead of a registry version range. On npm install, npm fetches whatever tarball that URL returns and installs it, running any lifecycle scripts contained in the fetched artifact. The source is unpinned, integrity-unchecked, and not the official npm registry; the shipped package body is a one-line stub, so the manifest itself is the entire delivery mechanism. The dependency key equals the package's own name and the version constraint (30.0.0) is implausibly high for a package of this size, matching the dependency-confusion smuggling shape where a high version number is used to win resolution against an internal package of the same name. Whoever controls repo.securityctrl.com controls code executed on the installer's machine at install time.
Source: ghsa-malware (6c9fcf70e683c61783b7bb2bd15645d130e85889507fc4c13133cf8544f464d0)
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": "65f6705e83e398e879f4769fe4207fd162acff160dfdd6cc755011bdc61672cb",
"tlsh": "f7e0c26449b1573312da03731839c597f3119e5b1404bd0de2cf0518428edf368f935c"
}
],
"package_integrity": [
{
"filename": "sentrykit-30.0.0.tgz",
"hashes": {
"sha1": "db940323982c55a0f67d672e4e2baee9db50fbe3",
"sha512_sri": "sha512-RHVe0leVAHBfo8v2Pm1mlo6IE654pUjD7RXJDtUDnPdXqCc1u/HCryjNtzw9+5aK2H9/5RwKfMM3C9oF7qTLYA=="
}
}
]
}
},
"package": {
"ecosystem": "npm",
"name": "sentrykit"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"versions": [
"30.0.0"
]
}
],
"aliases": [
"GHSA-qq6h-882h-g88f"
],
"credits": [
{
"contact": [
"inspector-research@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "IN-MAL-2026-019111",
"import_time": "2026-08-28T23:38:06.475142555Z",
"modified_time": "2026-08-28T23:17:48Z",
"sha256": "7070cc1752fa75b405bdd0617a934d29519df28fdd0d069c0d4b5f7adaf44f55",
"source": "amazon-inspector",
"versions": [
"30.0.0"
]
},
{
"id": "GHSA-qq6h-882h-g88f",
"import_time": "2026-08-29T18:26:29.98222335Z",
"modified_time": "2026-08-29T18:13:37Z",
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"sha256": "6c9fcf70e683c61783b7bb2bd15645d130e85889507fc4c13133cf8544f464d0",
"source": "ghsa-malware"
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (7070cc1752fa75b405bdd0617a934d29519df28fdd0d069c0d4b5f7adaf44f55)\npackage.json declares a self-referential dependency where the key `sentrykit` maps to the bare HTTPS URL `https://repo.securityctrl.com/sentrykit` instead of a registry version range. On `npm install`, npm fetches whatever tarball that URL returns and installs it, running any lifecycle scripts contained in the fetched artifact. The source is unpinned, integrity-unchecked, and not the official npm registry; the shipped package body is a one-line stub, so the manifest itself is the entire delivery mechanism. The dependency key equals the package\u0027s own name and the version constraint (30.0.0) is implausibly high for a package of this size, matching the dependency-confusion smuggling shape where a high version number is used to win resolution against an internal package of the same name. Whoever controls repo.securityctrl.com controls code executed on the installer\u0027s machine at install time.\n\n## Source: ghsa-malware (6c9fcf70e683c61783b7bb2bd15645d130e85889507fc4c13133cf8544f464d0)\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-15544",
"modified": "2026-08-29T18:28:24.965922484Z",
"published": "2026-08-28T23:17:48Z",
"references": [
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/sentrykit/v/30.0.0"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-qq6h-882h-g88f"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in sentrykit (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.