Critical Malicious Code Vulnerability in @devgandhi/healthpulse Package

@devgandhi/healthpulse Updated 03 Feb 2026

Summary

03/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-706: Malicious code in @devgandhi/healthpulse (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The @devgandhi/healthpulse package is an npm library designed for health monitoring functionalities. It allows developers to integrate health-related features into their applications. However, this package has been identified as containing malicious code, posing significant security risks to any system that utilizes it.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the @devgandhi/healthpulse package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it may lead to full control of the affected system by an external entity, making it crucial for users to take immediate action.

How To Fix

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

npm uninstall @devgandhi/healthpulse

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

Currently, there are no effective workarounds to mitigate the risks associated with this vulnerability other than removing the package entirely.

Conclusion

The @devgandhi/healthpulse package has been identified as containing malicious code that poses a significant security threat. Users are strongly advised to uninstall the package and take necessary precautions to secure their systems. Regular monitoring for vulnerabilities using tools like Vulert can help maintain the integrity of your software.

See every vulnerability recorded for @devgandhi/healthpulse →

Share this vulnerability

FAQ

You should immediately uninstall the package using 'npm uninstall @devgandhi/healthpulse' and rotate any secrets or keys stored on the affected system.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.

Failing to remove the package may leave your system vulnerable to unauthorized access and exploitation by malicious actors.

After removing the package, you should rotate all secrets and keys immediately from a secure system to mitigate potential damage.

Yes, consider looking for alternative packages that provide similar health monitoring functionalities without the associated risks.

How To Fix

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

npm uninstall @devgandhi/healthpulse

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