Malicious code in confluence-create-content (npm)
Historical advisory saved 24 Oct 2026 13:17:17 UTC. The publisher may have updated it since then. Latest advisory.
osv · MAL-2026-15530
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (011485304eea045bddd134da5fdabfcf9d96acd0f2c78e1800a4c32674a5788c) package.json declares a dependency whose key equals the package's own name (`confluence-create-content`) and whose value is a bare HTTPS URL, `https://repo.securityctrl.com/confluence-create-content`, instead of a registry version range. On `npm install`, npm fetches whatever bytes that URL returns and installs them, running any lifecycle scripts contained in them with no version pin and no integrity check. The shipped `index.js` is an inert stub, so the manifest URL is effectively the entire delivered payload. The self-named dependency shape also creates dependency-confusion pressure: any environment resolving this package name pulls content from the third-party host rather than the registry. ## Source: ghsa-malware (800bda35092bb13e9f61058c0df4ad6d43dc8f05e893129a79b3956c95fa6ee7) 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.
- Source published
- 28 Aug 2026 23:17:31 UTC
- Source modified
- 29 Aug 2026 18:45:18 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.