If this package is installed
Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.
Details
Source: amazon-inspector (e252184c7a4f29eafe72c86873c662342486b68fe5c1ce3a5405845aa8695a33)
package.json line 11 declares a dependency whose key equals the package's own name (`prm-bundles`) and whose value is a bare HTTPS URL (`https://repo.securityctrl.com/prm-bundles`) rather than a registry version range. On `npm install`, npm fetches whatever tarball that URL returns and installs it, executing any lifecycle scripts contained in it, with no version pin and no integrity check. Because the shipped source in this package is an inert placeholder, the manifest is the entire payload delivery mechanism, and the code that ultimately runs on the installer is whatever the operator of repo.securityctrl.com serves at install time. The implausibly high version (45.0.0) combined with the self-referential name is consistent with a dependency-confusion redirection targeting an internal package name.
Source: ghsa-malware (007c18a94d026725fe4a18ea8c629fb9b1d53f5eff378b671386961dd03657ed)
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.