This report shows the evidence for retry-utils-testmetest@1.0.3. 1 of 4 known versions is blocked or flagged. The newest version, 1.0.5, is allowed.
Blocked by malware advisory
OpenSSF/OSV malware advisory MAL-2026-20279 identifies this version as malicious and supplies the Firewall block.
What to do: remove this version and, if it ran, rotate the credentials it could reach. Remediation↓
OpenSSF/OSV malicious advisory
published · by OpenSSF/OSV
OpenSSF/OSV advisory MAL-2026-20279 confirms this npm version as malicious.
Advisory
MAL-2026-20279
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in retry-utils-testmetest (npm)
Details
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.
This report applies to retry-utils-testmetest@1.0.3.
The versions list below shows the verdict for each recorded version.
Avoid installing retry-utils-testmetest@1.0.3. Remove it from direct dependencies and check your lockfile for transitive copies.
Choose an independently verified alternative or release. This report does not establish that other versions are safe.
If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.