# MAL-2026-15546: Malicious code in vui-gateway (npm)


- **Type:** Malicious package
- **Package:** `vui-gateway` (npm)
- **Published:** 28 Aug 2026
- **Also known as:** GHSA-69cq-ggff-w363

## What is MAL-2026-15546?

MAL-2026-15546 is a malicious package in vui-gateway, published on 28 Aug 2026. 

### Official description

package.json declares a dependency whose key equals this package's own name (`vui-gateway`) and whose source is an off-registry HTTPS URL, `https://repo.securityctrl.com/vui-gateway`. On `npm install`, npm resolves that URL and installs whatever bytes it returns, running any lifecycle scripts contained within. The source is not the npm registry, there is no version pin, and no integrity hash is present, so the content is mutable and unauthenticated — whoever controls `repo.securityctrl.com` controls code execution on the installer's machine. The shipped index.js is an inert stub; the manifest itself is the entire attack surface. The dependency-key-equals-package-name shape is characteristic of dependency-confusion attacks intended to shadow an internal package of the same 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-15546?

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

## Sources

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

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