Which versions of testmgkregme are malicious?

The following npm versions of testmgkregme are flagged malicious: 1.0.1. Treat any of these as compromised.

How do I remediate testmgkregme if I installed it?

Remove testmgkregme from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed testmgkregme — how do I know if it already compromised me?

If testmgkregme was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is testmgkregme part of a known attack campaign?

Yes — testmgkregme is associated with the IN-MAL-2026-020213 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find testmgkregme across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for testmgkregme (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging testmgkregme across your stack and pipelines.

Malicious package

testmgkregmenpm

testmgkregme is a confirmed malicious npm package (MAL-2026-16317) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in testmgkregme (npm)

MAL-2026-16317

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall testmgkregme

What this malware does

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 evals 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.

Malicious versions

1 flagged

1.0.1

Indicators of compromise (SHA-256)

496e8021fd5e2626c503e2ceeed8349ff15c68c71a5f19d8a57c67e5f1b41863

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for testmgkregme (version 1.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging testmgkregme across your stack and pipelines.
If you installed it — respond
Remove testmgkregme from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If testmgkregme was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks testmgkregme before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. testmgkregme on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020213

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks testmgkregme-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database