# MAL-2026-15543: Malicious code in prm-bundles (npm)


- **Type:** Malicious package
- **Package:** `prm-bundles` (npm)
- **Published:** 28 Aug 2026
- **Also known as:** GHSA-g57v-rj8p-j52h

## What is MAL-2026-15543?

MAL-2026-15543 is a malicious package in prm-bundles, published on 28 Aug 2026. 

### Official description

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.

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.

## What should I do about MAL-2026-15543?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-15543 is a malicious package: prm-bundles (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-15543/ (Markdown: https://insights.sbomify.com/MAL-2026-15543/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-15543

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-15543/
Summaries are generated and may contain mistakes; the official description above is the record.