Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

log-rotate-testmetestnpm

Advisory published Updated

log-rotate-testmetest is a confirmed malicious npm package (MAL-2026-18185) 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 log-rotate-testmetest (npm)

MAL-2026-18185
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall log-rotate-testmetest

What this malware does

The package ships a binding.gyp whose sources field uses GYP command-expansion (<!(env node index.js...)) with no native source files, causing npm's implicit node-gyp rebuild to execute index.js at install time. index.js is a Caesar+10 (ROT) obfuscated eval blob that, once decoded, AES-128-GCM-decrypts a hardcoded hex ciphertext and the sibling data.bin, brotli-decompresses the result, writes it to a mkdtemp'd temporary file, and spawns it under Bun (Bun.spawn([execPath,'run',tmp]) / spawn(getBunPath(),['run',tmp])). package.json declares bun as a runtime dependency, deliberately routing execution through an alternate runtime rather than Node. The executed payload is fully opaque and attacker-controlled. The combination of a no-source binding.gyp used solely as a lifecycle trigger, multi-layer obfuscation (ROT + AES-GCM + brotli), and alternate-runtime dispatch has no legitimate native-build justification.

Malicious versions

1 flagged
1.0.1

Indicators of compromise (SHA-256)

8608133ab1a2f106c095f84116cd25fa141208dbf81ea6fe2331e38a88551a4b

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for log-rotate-testmetest (version 1.0.1).

  2. If you installed it — respond

    Remove log-rotate-testmetest 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.

  3. Did it already run?

    If log-rotate-testmetest was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. log-rotate-testmetest 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-021577

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks log-rotate-testmetest-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.

Explore

log-rotate-testmetest (npm) malicious package — MAL-2026-18185 | O3 Security