jira-projects-backbonenpm

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.