# MAL-2026-16317: Malicious code in testmgkregme (npm)


- **Type:** Malicious package
- **Package:** `testmgkregme` (npm)
- **Published:** 21 Sep 2026
- **Also known as:** GHSA-x8qg-wc79-vfhh

## What is MAL-2026-16317?

MAL-2026-16317 is a malicious package in testmgkregme, published on 21 Sep 2026. 

### Official description

npm package testmgkregme@1.0.1 uses a binding.gyp whose `sources` field employs GYP command-expansion (`<!(env node index.js...; echo stub.c)`) to run `node index.js` during `node-gyp rebuild`, which npm invokes automatically when a binding.gyp is present. No native source files (.c/.cc/.cpp/.h) are shipped, so the binding.gyp exists solely to trigger install-time code execution rather than to build a native addon. The executed index.js is a 2.9 MB single-IIFE wrapper: an outer Caesar-cipher (ROT k=4) layer is passed to `eval`, and the decoded body then AES-128-GCM-decrypts hardcoded hex ciphertexts with a hardcoded key/IV/authTag and `eval`s the plaintext. The multi-layer ROT->eval->AES->eval construction has no legitimate purpose and conceals the runtime payload from static review. The result is that `npm install testmgkregme` causes opaque attacker-authored JavaScript to execute on the installer's machine with the installer's privileges.

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

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

## Sources

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

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