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

rust-testing-utilsnpm

Advisory published Updated

rust-testing-utils is a confirmed malicious npm package (MAL-2026-14374) that opens a backdoor for remote access (malicious version 2.3.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in rust-testing-utils (npm)

MAL-2026-14374
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall rust-testing-utils

What this malware does

The package impersonates the pino logger in its README, keywords, and API surface. index.js exports middleware that spawns lib/caller.js as a detached child process on invocation. caller.js reconstructs a hardcoded URL by base64-decoding a value stored under a fake process.env.DEV_API_KEY inside a fabricated process object, resolving to https://api.jsonstorage.net/v1/json/2ef8c758-a96f-459e-b036-b3b90379a165/f89e8264-86c2-4684-94da-c3f82d59370f. It fetches this URL with axios and passes the returned cookie field to new Function.constructor("require", s), then invokes the resulting function with require as an argument, giving the remotely fetched code arbitrary execution with full module-loading capability in the consumer's process. The endpoint content is attacker-controlled and mutable, so the executed payload can change at any time without a package update. The base64-encoded URL, fabricated env-var names used to hide the destination, and pino-lookalike cover story are consistent with an intentional supply-chain attack rather than legitimate functionality.

Malicious versions

1 flagged
2.3.0

Indicators of compromise (SHA-256)

ee33bdedc7938508bcb50e053c441770948d3d69a51c5cab5d4280d84ceffa65

Detection & response playbook

Backdoor / remote access
  1. Find it

    Search your lockfiles and build artifacts for rust-testing-utils (version 2.3.0).

  2. If you installed it — respond

    rust-testing-utils 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 rust-testing-utils 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. rust-testing-utils on npm has been identified as a malicious package (version 2.3.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-018568

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks rust-testing-utils-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

rust-testing-utils (npm) malicious package — MAL-2026-14374 | O3 Security