# MAL-2026-16416: Malicious code in @tvg-mar/utils (npm)


- **Type:** Malicious package
- **Package:** `@tvg-mar/utils` (npm)
- **Published:** 22 Sep 2026
- **Also known as:** GHSA-p6w4-mmhj-wc4v

## What is MAL-2026-16416?

MAL-2026-16416 is a malicious package in @tvg-mar/utils, published on 22 Sep 2026. 

### Official description

package.json declares scripts.install="node index.js", which loads runtime/index.js and then support/telemetry/probe/impl.js. That module reconstructs Node core APIs ('os', 'dns', 'process', 'userInfo', 'hostname', 'cwd', 'resolve4') and its destination domain from hex/char-code arrays at runtime, reads os.userInfo().username, os.hostname(), and process.cwd(), and encodes those values as labels of a subdomain under oob.algamil7x.xyz queried via dns.resolve4 — a DNS out-of-band exfiltration channel that fires automatically on npm install. Method names and the destination host are split across sibling files (d5a8c1.js, e6b9d2.js) and disguised with cover-story comments describing a benign 'registry mirror connectivity probe'.

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

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-16416 is a malicious package: @tvg-mar/utils (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-16416/ (Markdown: https://insights.sbomify.com/MAL-2026-16416/index.md)
```

## Sources

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

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