Critical Malicious Code Vulnerability in @devgandhi/cpp Package

@devgandhi/cpp Updated 03 Feb 2026

Summary

03/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-705: Malicious code in @devgandhi/cpp (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 @devgandhi/cpp package is an npm library designed for C++ development, providing various utilities and functionalities for developers. However, it has been compromised, embedding malicious code that poses significant security risks to any system utilizing this package. Users of this package should be aware of its potential to expose sensitive information and grant unauthorized access to external entities.

Vulnerability Detail

The vulnerability originates from the presence of malicious code within the @devgandhi/cpp package. This code can fully compromise any computer where the package is installed, allowing attackers to access secrets and keys stored on the system. The implications of this vulnerability are severe, as it may lead to data breaches and unauthorized control over the affected systems. The malicious nature of the code is classified under CWE-506, indicating that it contains embedded malicious code.

How To Fix

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

npm uninstall @devgandhi/cpp

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. The only recommended action is to uninstall the compromised package.

Conclusion

The @devgandhi/cpp package has been identified as containing malicious code, posing significant security risks to systems that utilize it. Immediate uninstallation of the package and rotation of sensitive information is essential to mitigate potential damage. Users are encouraged to utilize tools like Vulert for ongoing monitoring of vulnerabilities in their applications.

See every vulnerability recorded for @devgandhi/cpp →

Share this vulnerability

FAQ

Immediately uninstall the package using 'npm uninstall @devgandhi/cpp' and rotate any sensitive information stored on the affected system.

You can use Vulert's playground at Vulert Scanner to monitor and check for vulnerabilities in your application without requiring any signup.

Keeping this package installed can lead to unauthorized access to your system, data breaches, and potential control by malicious actors.

No, there is currently no patched version available for the @devgandhi/cpp package. The only option is to uninstall it.

Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software, ensuring you stay informed about potential risks.

How To Fix

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

npm uninstall @devgandhi/cpp

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