jira-projects-backbone

Details

**Severity:** Critical

**Affected versions:** `= 45.0.0`

## Source: amazon-inspector (f75bb5293b51dc977d699982756ea69987397ce86f50d12753844198bf40294c)
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`.

---

Credit: [OpenSSF](https://github.com/ossf/malicious-packages) ([source](https://github.com/ossf/malicious-packages/blob/d75ebb673b0185a99abe46e9e4a60aaa467fa7d8/osv/malicious/npm/jira-projects-backbone/MAL-2026-15537.json))

**References:**
- https://github.com/ossf/malicious-packages/blob/d75ebb673b0185a99abe46e9e4a60aaa467fa7d8/osv/malicious/npm/jira-projects-backbone/MAL-2026-15537.json
- https://www.npmjs.com/package/jira-projects-backbone/v/45.0.0
- https://github.com/advisories/GHSA-mgjj-8534-64gp

Compromised versions (1)

• = 45.0.0

Any computer that installed or ran a compromised version should be considered fully compromised. Rotate every secret on that machine from a clean environment.