jira-projects-backbonenpm
jira-projects-backbone is a confirmed malicious npm package (MAL-2026-15537) that executes malicious code on install (malicious version 45.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in jira-projects-backbone (npm)
What this malware does
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for jira-projects-backbone (version 45.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging jira-projects-backbone across your stack and pipelines.
If you installed it — respond
Remove jira-projects-backbone from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If jira-projects-backbone was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks jira-projects-backbone before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks jira-projects-backbone-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.