# MAL-2026-10150: Malicious code in ap3-components-ui (npm)


- **Type:** Malicious package
- **Package:** `ap3-components-ui` (npm)
- **Published:** 10 Jul 2026
- **Also known as:** GHSA-qhgr-v9vh-3784

## What is MAL-2026-10150?

MAL-2026-10150 is a malicious package in ap3-components-ui, published on 10 Jul 2026. 

### Official description

Package 'ap3-components-ui' at version 9.999.0 declares a preinstall hook ("node index.js > /dev/null 2>&1") that shells out to collect installer-side identifiers — hostname, current working directory, username, and the installer's public IP (fetched via curl to ifconfig.me) — hex-encodes the collected data, and exfiltrates it as DNS subdomain queries under d987f5ra3q1r1j7ahol0yzuwujwe76i55.oast.fun, an attacker-controlled Interactsh collector. The package name is also embedded in the beacon payload so the operator can correlate which internal name resolved externally. The tarball has an empty description, no README, and no library code beyond the exfil script — the canonical shape of a dependency-confusion squat on an internal package name, published at the sentinel version 9.999.0 to force resolution over any legitimate internal release.

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

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

## Sources

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

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