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

node-runtime-utilsnpm

node-runtime-utils is a confirmed malicious npm package (MAL-2026-14313) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in node-runtime-utils (npm)

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

What this malware does

The package was found to contain malicious code or consuming dependency that contains malicious code

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged
1.0.0

Indicators of compromise (SHA-256)

14921c39b1bbfdf7d3e80f80316be37300a46ef6f16fe9597a22464bbb3034ff
cac7a39a8896a7f78a20fe79758f146d2158f2fc529e51ac705720a745552770

Detection & response playbook

Malicious package
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for node-runtime-utils (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging node-runtime-utils across your stack and pipelines.

  2. If you installed it — respond

    Remove node-runtime-utils 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.

  3. Did it already run?

    If node-runtime-utils was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

  4. How O3 protects you

    O3 blocks node-runtime-utils before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. node-runtime-utils on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-c436-rrhg-m984IN-MAL-2026-018441

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks node-runtime-utils-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.

Explore