mal-2026-15531
Vulnerability from ossf_malicious_packages
-= Per source details. Do not edit below this line.=-
Source: amazon-inspector (e7615f50c489336db7800ea3b79ef26a4e5af311f0484ee31871000e329c2813)
package.json declares a dependency whose value is a bare HTTPS URL (https://repo.securityctrl.com/confluence-editor) rather than a semver range published to the npm registry. The dependency key equals the package's own name, matching a dependency-confusion shape, and the version 30.0.0 is implausibly high for a package of this name. On npm install, npm fetches whatever tarball that URL currently returns and executes any lifecycle scripts inside it, with no version pin, no integrity check, and no registry provenance. The shipped index.js is an inert stub, so the manifest line itself is the entire published attack surface — the actual code that runs on installers is served from repo.securityctrl.com and can be changed by whoever controls that host at any time.
Source: ghsa-malware (337c533edd7c73d6e29a4f5a891207c3825eddb4187935e0cca00b94efd46c97)
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": "caf33006f94348ea14292b25d7f146db52a7d363508304674ea67bd5e3d161a4",
"tlsh": "78e07d294d104b330fc906634879548773554e9f20083d0896cf883c405e9b3bafe37d"
}
],
"package_integrity": [
{
"filename": "confluence-editor-30.0.0.tgz",
"hashes": {
"sha1": "5e1c5166096adfcdb0ad65e9e828f618817b4e46",
"sha512_sri": "sha512-g0bnxe2wDLSjhy5fwXrFPeH4Sp9++SiLPkYujAuY3OPjUlTvxwVP+Wc0XTuxLudAJpND8W6g0jOQc7M6cWikOQ=="
}
}
]
}
},
"package": {
"ecosystem": "npm",
"name": "confluence-editor"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"versions": [
"30.0.0"
]
}
],
"aliases": [
"GHSA-cwcw-cv28-7jfm"
],
"credits": [
{
"contact": [
"inspector-research@amazon.com"
],
"name": "Amazon Inspector",
"type": "FINDER"
}
],
"database_specific": {
"malicious-packages-origins": [
{
"id": "IN-MAL-2026-019107",
"import_time": "2026-08-28T23:38:06.100735411Z",
"modified_time": "2026-08-28T23:17:15Z",
"sha256": "e7615f50c489336db7800ea3b79ef26a4e5af311f0484ee31871000e329c2813",
"source": "amazon-inspector",
"versions": [
"30.0.0"
]
},
{
"id": "GHSA-cwcw-cv28-7jfm",
"import_time": "2026-08-29T18:26:29.956364657Z",
"modified_time": "2026-08-29T18:13:37Z",
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "SEMVER"
}
],
"sha256": "337c533edd7c73d6e29a4f5a891207c3825eddb4187935e0cca00b94efd46c97",
"source": "ghsa-malware"
}
]
},
"details": "\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (e7615f50c489336db7800ea3b79ef26a4e5af311f0484ee31871000e329c2813)\npackage.json declares a dependency whose value is a bare HTTPS URL (https://repo.securityctrl.com/confluence-editor) rather than a semver range published to the npm registry. The dependency key equals the package\u0027s own name, matching a dependency-confusion shape, and the version 30.0.0 is implausibly high for a package of this name. On npm install, npm fetches whatever tarball that URL currently returns and executes any lifecycle scripts inside it, with no version pin, no integrity check, and no registry provenance. The shipped index.js is an inert stub, so the manifest line itself is the entire published attack surface \u2014 the actual code that runs on installers is served from repo.securityctrl.com and can be changed by whoever controls that host at any time.\n\n## Source: ghsa-malware (337c533edd7c73d6e29a4f5a891207c3825eddb4187935e0cca00b94efd46c97)\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-15531",
"modified": "2026-08-29T18:28:21.140505630Z",
"published": "2026-08-28T23:17:15Z",
"references": [
{
"type": "PACKAGE",
"url": "https://www.npmjs.com/package/confluence-editor/v/30.0.0"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-cwcw-cv28-7jfm"
}
],
"schema_version": "1.7.4",
"summary": "Malicious code in confluence-editor (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.