Malicious code in runtime-health (npm)
The npm package runtime-health version 1.0.2 was identified as malicious by the OpenSSF Package Analysis project. The package executes commands associated with malicious behavior.
- Disclosed
- Last updated
- Blast radius
- All users who installed runtime-health version 1.0.2
- Ecosystems
- Attack vectors
- Affected entities
- runtime-health · 1.0.2
The OpenSSF Package Analysis project identified runtime-health version 1.0.2 on npm as containing malicious code. The package was flagged for executing one or more commands associated with malicious behavior.\n\nThe malicious package was published to the npm registry and could have been installed by any user or project that explicitly depended on this version. The OpenSSF malicious-packages repository has documented this incident with identifier MAL-2026-14116.\n\nThis is a direct supply chain compromise where malicious code was introduced into a published npm package, potentially affecting all downstream consumers who installed the affected version.
Indicators of compromise
- Packages
- runtime-health@1.0.2
Remediation
- Immediately remove runtime-health version 1.0.2 from all projects and dependencies
- Audit all systems where runtime-health 1.0.2 was installed for signs of compromise or malicious activity
- Review npm audit logs and package-lock.json files to identify all installations of this version
- Update to a safe version of runtime-health if available, or replace with an alternative package
- Monitor for any suspicious behavior on systems that may have executed this malicious package
Sources
- GitHub Advisory GHSA-fg74-5f33-c553 · GitHub Advisory Database
Cite this entry
"Malicious code in runtime-health (npm)." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 18, 2026; last updated August 18, 2026. https://supplychainattack.org/incident/malicious-code-in-runtime-health-npm-rvh4zo
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in 3-buildsight-web (npm)
The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.
npmCompromised package - resolvedcritical
Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)
Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.
npmDependency confusionCompromised package - resolvedcritical
Malicious code in create-coin (npm)
create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.
npmCompromised packageTyposquatting - resolvedcritical
Malicious code in @syncraft-labs/vue (npm)
The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.
npmCompromised package