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

testrrrdnpm

Advisory published Updated

testrrrd is a confirmed malicious npm package (MAL-2026-17706) that opens a backdoor for remote access (malicious versions 0.0.1, 1.0.0, 1.1.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in testrrrd (npm)

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

What this malware does

On npm install, package.json scripts.postinstall runs node beacon.cjs, which POSTs a JSON payload containing the installer's hostname (os.hostname()), install path (__dirname), current working directory (process.cwd()), Node version, and package identifier over plain HTTP to the hardcoded bare-IP endpoint http://185.158.107.175:8787/_ah/dc. The same beacon is re-triggered at import time: index.js (the declared main) calls require('./beacon.cjs').fire() and then exports a Proxy whose get trap returns a no-op for any member access, so consumers importing arbitrary names from the package continue past the callback. The dual trigger ensures the callback fires even when lifecycle scripts are suppressed (e.g. npm install --ignore-scripts), and the Proxy shim conceals that the package provides no legitimate functionality. The destination is a bare IPv4 address on a non-standard port unrelated to any declared publisher, and the transport is unencrypted.

Malicious versions

7 flagged
0.0.11.0.01.1.02.0.02.0.13.0.099.0.1

Indicators of compromise (SHA-256)

016351de268cd01a6a8f3cb2278b3735206e45c254b3b166c18bc0bf4abf17b6
84a7f8fd9d6de2f68ce889aa54d7492bbb2f7a4ac7c78542b27bb41cbb119a34
91a77cc9dbdff4799414082dc85fc6581b9f2d7297136dea8c50540f7d5244ad
e94d33713dfab2a5d24334bd4dfc9f840fe8357174a540134724097d9da92156
f3acddc2a24a30fe2bbb66b02f5da938bb888824a127915df5c86faec95ffe10
0b2b8898408042377780b7012071a760128d4fcd83d0a3230cd1619036b427ed
767b0c5bd1f7cbd076d5564c333485255f96fe58c834757cf73d5d25c8d5c911

Detection & response playbook

Backdoor / remote access
  1. Find it

    Search your lockfiles and build artifacts for testrrrd (7 malicious versions).

  2. If you installed it — respond

    testrrrd establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

  3. Did it already run?

    If testrrrd 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. testrrrd on npm has been identified as a malicious package (versions 0.0.1, 1.0.0, 1.1.0, 2.0.0, 2.0.1, 3.0.0, 99.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021260IN-MAL-2026-021257IN-MAL-2026-021259IN-MAL-2026-021267IN-MAL-2026-021258IN-MAL-2026-021256IN-MAL-2026-021266

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks testrrrd-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Explore

testrrrd (npm) malicious package — MAL-2026-17706 | O3 Security