# MAL-2026-15516: Malicious code in nx-app (npm)


- **Type:** Malicious package
- **Package:** `nx-app` (npm)
- **Published:** 28 Aug 2026
- **Also known as:** GHSA-h9j7-rx3x-rwhc, GHSA-vmrp-3pwx-mj42

## What is MAL-2026-15516?

MAL-2026-15516 is a malicious package in nx-app, published on 28 Aug 2026. 

### Official description

package.json declares its own name `nx-app` as a dependency whose value is a raw HTTPS URL (`https://repo.securityctrl.com/nx-app`) rather than a semver range against the npm registry. On `npm install`, npm fetches a tarball from that URL and runs any lifecycle scripts it contains, with no version pin, no integrity hash, and no signature check. Whoever controls repo.securityctrl.com controls code executed on the installer's machine at install time. The self-referential dependency key (matching the package's own name) is a dependency-confusion shape that forces resolution to the off-registry URL even when a registry-hosted `nx-app` exists, and the shipped in-tree source is an inert stub so the manifest URL is the sole payload delivery vector.

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

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

## Sources

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

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