What does the runtime-health malware do?

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.

Which versions of runtime-health are malicious?

The following npm versions of runtime-health are flagged malicious: 1.0.1, 1.0.2, 1.0.4. Treat any of these as compromised.

How do I remediate runtime-health if I installed it?

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.

I already installed runtime-health — how do I know if it already compromised me?

If runtime-health 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.

How do I find runtime-health across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for runtime-health (3 malicious versions).

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

Find it
Search your lockfiles and build artifacts for runtime-health (3 malicious versions).
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.
Did it already run?
If runtime-health 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. 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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database