# MAL-2026-15530: Malicious code in confluence-create-content (npm)


- **Type:** Malicious package
- **Package:** `confluence-create-content` (npm)
- **Published:** 28 Aug 2026
- **Also known as:** GHSA-j52x-8r24-hw6x

## What is MAL-2026-15530?

MAL-2026-15530 is a malicious package in confluence-create-content, published on 28 Aug 2026. 

### Official description

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.

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.

## What should I do about MAL-2026-15530?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-15530 is a malicious package: confluence-create-content (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-15530/ (Markdown: https://insights.sbomify.com/MAL-2026-15530/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-15530

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-15530/
Summaries are generated and may contain mistakes; the official description above is the record.