prm-bundles

Details

**Severity:** Critical

**Affected versions:** `= 45.0.0`

## 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.

---

Credit: [OpenSSF](https://github.com/ossf/malicious-packages) ([source](https://github.com/ossf/malicious-packages/blob/d75ebb673b0185a99abe46e9e4a60aaa467fa7d8/osv/malicious/npm/prm-bundles/MAL-2026-15543.json))

**References:**
- https://github.com/ossf/malicious-packages/blob/d75ebb673b0185a99abe46e9e4a60aaa467fa7d8/osv/malicious/npm/prm-bundles/MAL-2026-15543.json
- https://www.npmjs.com/package/prm-bundles/v/45.0.0
- https://github.com/advisories/GHSA-x86v-25gf-7xc2

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.