# MAL-2026-16255: Malicious code in randompkga (npm)


- **Type:** Malicious package
- **Package:** `randompkga` (npm)
- **Published:** 17 Sep 2026
- **Also known as:** GHSA-532p-c872-3926

## What is MAL-2026-16255?

MAL-2026-16255 is a malicious package in randompkga, published on 17 Sep 2026. 

### Official description

package.json declares a postinstall lifecycle script `cd "$INIT_CWD" && npm i randompkgb` that, on `npm install`, installs the additional npm package `randompkgb` into the consumer's project. A companion postinstall.js reads the installer's own package.json at $INIT_CWD, sets `dependencies.randompkgb = "^1.0.0"`, and writes the manifest back to disk, persisting the injected dependency across future installs and CI runs. The caret range is unpinned, so any current or future version of `randompkgb` — whose code is not present in this package and is not controlled by the installer — will be resolved and executed on the installer's machine at install time and on `require`. This is dependency-tree hijacking: the mechanism drops attacker-controlled third-party code into the installer's environment and rewrites source-controlled project state to make the injection durable.

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-16255?

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-16255 is a malicious package: randompkga (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-16255/ (Markdown: https://insights.sbomify.com/MAL-2026-16255/index.md)
```

## Sources

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

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