Malicious code in testmgkregme (npm)

CISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.

No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (496e8021fd5e2626c503e2ceeed8349ff15c68c71a5f19d8a57c67e5f1b41863) npm package [email protected] 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. ## Source: ghsa-malware (232bcd8cfd23f7b114b95fb7b57074ef43203a0f27579ab9dd475dec57a87f6e) 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.

Source published

21 Sep 2026 03:23:55 UTC

Source modified

12 Oct 2026 13:45:04 UTC

Observed here

24 Oct 2026 13:17:17 UTC

Source terms

OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.