retry-utils-testmetestnpm
Advisory published Updated
retry-utils-testmetest is a confirmed malicious npm package (MAL-2026-20279) that executes malicious code on install (malicious version 1.0.3). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in retry-utils-testmetest (npm)
What this malware does
The package advertises itself as a lightweight retry utility but ships no library code consistent with that purpose. binding.gyp declares a stub target with no native sources (.c/.cc/.cpp) and uses GYP command-expansion syntax (<!(node index.js...)) in an action, causing npm's automatic node-gyp rebuild to execute index.js at install time. index.js is a multi-layer obfuscated loader: a Caesar-shifted string is passed to eval; the decoded loader AES-128-GCM-decrypts an in-file blob (yielding a getBunPath helper), then AES-128-GCM-decrypts and brotli-decompresses lib_native.dat into a second-stage script, writes it to a temporary file, and spawns it. Execution is routed through the Bun runtime (via getBunPath()) rather than Node, evading Node-based install-time inspection. The ~319 KB lib_native.dat is named to masquerade as a native shared library but contains high-entropy AES-128-GCM ciphertext with no plaintext strings. The combination — stub binding.gyp with no native sources used only to trigger install-time execution, Caesar+AES+Brotli layered obfuscation, encrypted payload disguised as a native library, and alternate-runtime execution via Bun — is a dropper delivering attacker-controlled code to any machine that runs npm install on this package.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Malicious packageFind it
Search your lockfiles and build artifacts for retry-utils-testmetest (version 1.0.3).
If you installed it — respond
Remove retry-utils-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.
Did it already run?
If retry-utils-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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks retry-utils-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.