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

runtime-healthnpm

runtime-health is a confirmed malicious npm package (MAL-2026-14116) that executes malicious code on install (malicious versions 1.0.1, 1.0.2, 1.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in runtime-health (npm)

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

What this malware does

The OpenSSF Package Analysis project identified 'runtime-health' @ 1.0.2 (npm) as malicious.

It is considered malicious because:

  • The package executes one or more commands associated with malicious behavior.

Malicious versions

3 flagged
1.0.11.0.21.0.4

Indicators of compromise (SHA-256)

947c67500453c29daa330afc7d05e5ab5eb6405c4da235d1d0b408b247489832
d9e71daa18c5918df751c2c556f352736fefba535c8ed612faed227ebd8eda40
dd172704e1a61ef5a2a016258136478465a1bd13cd3c5a2b697a2c9b76078afc

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 runtime-health (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging runtime-health across your stack and pipelines.

  2. If you installed it — respond

    Remove runtime-health 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 runtime-health 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 runtime-health 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. runtime-health on npm has been identified as a malicious package (versions 1.0.1, 1.0.2, 1.0.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

  • OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks runtime-health-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

runtime-health (npm) malicious package — MAL-2026-14116 | O3 Security