Critical Malicious Code Vulnerability in health-check-node Package

health-check-node Updated 20 Jan 2026

Summary

20/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-362: Malicious code in health-check-node (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The health-check-node package is an npm module designed to facilitate health checks for Node.js applications. It is commonly used in various web applications to ensure that services are running smoothly. However, this package has been compromised, leading to severe security risks for any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the health-check-node package. This code can fully compromise any computer that has the package installed or running. It poses a significant risk as it can access sensitive information, including secrets and keys stored on the affected system. The malicious nature of this code is classified under CWE-506, indicating that it contains embedded malicious code that can lead to unauthorized access and control over the system.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall health-check-node

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There are no effective workarounds for this vulnerability. The only recommended action is to uninstall the health-check-node package and secure your system.

Conclusion

The health-check-node package has been compromised with malicious code, posing a significant threat to any system using it. Immediate removal of the package and rotation of sensitive information is essential to mitigate risks. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for health-check-node →

Share this vulnerability

FAQ

You should immediately uninstall the health-check-node package and rotate any sensitive information stored on the affected system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential control by malicious entities.

There are no effective mitigation strategies available. The only safe course of action is to remove the package entirely.

Vulert provides a service that monitors your package-lock.json file for open-source vulnerabilities in real-time, alerting you to any issues.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall health-check-node

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback