# MAL-2026-16359: Malicious code in @uh-platform/domain-widget (npm)


- **Type:** Malicious package
- **Package:** `@uh-platform/domain-widget` (npm)
- **Published:** 21 Sep 2026
- **Also known as:** GHSA-c842-qvgg-5vpf

## What is MAL-2026-16359?

MAL-2026-16359 is a malicious package in @uh-platform/domain-widget, published on 21 Sep 2026. 

### Official description

Package @uh-platform/domain-widget@100.0.0 is a scoped placeholder with an empty author, generic description, and no real functionality. Its package.json declares scripts.preinstall = "node index.js", and index.js shells out via exec() to curl a hardcoded Burp Collaborator subdomain at http://pa33pg1od9cr4ffnrzec8864jvpmdd12.oastify.com/. On `npm install`, the installer's host performs a DNS+HTTP request to that attacker-controlled OAST endpoint, disclosing the installer's IP and host presence and confirming out-of-band code execution on the build machine. The `@uh-platform` scope combined with an inflated 100.0.0 version, empty metadata, and a preinstall-only payload is the canonical dependency-confusion shape targeting an internal namespace to shadow a private package during resolution.

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

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-16359 is a malicious package: @uh-platform/domain-widget (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-16359/ (Markdown: https://insights.sbomify.com/MAL-2026-16359/index.md)
```

## Sources

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

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