# MAL-2026-15537: Malicious code in jira-projects-backbone (npm)


- **Type:** Malicious package
- **Package:** `jira-projects-backbone` (npm)
- **Published:** 28 Aug 2026
- **Also known as:** GHSA-8569-7m7w-7gf9

## What is MAL-2026-15537?

MAL-2026-15537 is a malicious package in jira-projects-backbone, published on 28 Aug 2026. 

### Official description

package.json line 11 declares a dependency whose key equals the package's own name (`jira-projects-backbone`) with a value that is a bare HTTPS URL, `https://repo.securityctrl.com/jira-projects-backbone`, instead of a registry version range. On `npm install`, npm fetches whatever tarball that URL returns and installs it, running any lifecycle scripts it contains, with no version pin and no integrity check. The shipped source in this package is an inert stub, so the manifest itself is the entire install-time surface — every install resolves to attacker-controlled code from repo.securityctrl.com. The self-name reuse and implausibly high version (45.0.0) also give this manifest a dependency-confusion shape against any internal package named `jira-projects-backbone`.

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-15537?

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-15537 is a malicious package: jira-projects-backbone (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-15537/ (Markdown: https://insights.sbomify.com/MAL-2026-15537/index.md)
```

## Sources

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

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