MAL-2026-18185 Malicious code in log-rotate-testmetest (npm)
Malicious package
Published
MAL-2026-18185 is a malicious package: log-rotate-testmetest (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-18185/ (Markdown: https://insights.sbomify.com/MAL-2026-18185/index.md)
- Package
- log-rotate-testmetest
- Registry
- npm
What is MAL-2026-18185?
MAL-2026-18185 is a malicious package in log-rotate-testmetest, published on 22 Oct 2026.
Official description
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.What should I do about MAL-2026-18185?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.