# MAL-2026-16412: Malicious code in @tvg-mar/promos-context (npm)


- **Type:** Malicious package
- **Package:** `@tvg-mar/promos-context` (npm)
- **Published:** 22 Sep 2026
- **Also known as:** GHSA-f42w-v662-25cr

## What is MAL-2026-16412?

MAL-2026-16412 is a malicious package in @tvg-mar/promos-context, published on 22 Sep 2026. 

### Official description

The package's `install` lifecycle script runs `node index.js`, which loads `runtime/support/telemetry/probe/impl.js`. On every `npm install`, that module dynamically resolves the `os` and `dns` core modules via `module.constructor._load` with char-code-obfuscated names, reads `os.userInfo().username`, `os.hostname()`, and the basename of `process.cwd()`, and encodes them as DNS labels in a `dns.resolve4` query to `oob.algamil7x.xyz`. The destination domain is reconstructed at runtime from a hex char-code array in `runtime/support/telemetry/probe/d4c8a1.js` / `e5d9b2.js` rather than appearing as a plain string. The combination of an install-time hook, obfuscated core-module loading, obfuscated destination, and DNS-tunnel encoding of installer identity fields is a classic install-time exfiltration beacon.

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

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

## Sources

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

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