prm-bundlesnpm
prm-bundles is a confirmed malicious npm package (MAL-2026-15543) 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 prm-bundles (npm)
What this malware does
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.
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 prm-bundles (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 prm-bundles across your stack and pipelines.
If you installed it — respond
Remove prm-bundles 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 prm-bundles 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 prm-bundles 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 prm-bundles-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.