Critical Malicious Code Vulnerability in graphflowx Package

graphflowx Updated 10 Feb 2026

Summary

10/02/2026
CRITICAL
No i
Critical
Not published

MAL-2026-834: Malicious code in graphflowx (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 graphflowx package is an npm library designed for graph data processing and visualization. It provides developers with tools to create and manipulate graph structures efficiently. However, this package has been identified as containing malicious code that compromises the security of any system it is installed on.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the graphflowx package. This code can lead to full system compromise, allowing unauthorized access to sensitive data, including secrets and keys stored on the affected machine. The presence of this malicious code is classified under CWE-506, indicating that it contains embedded malicious code that poses significant risks to users and their systems.

How To Fix

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

npm uninstall graphflowx

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 other than removing the package entirely. Users should ensure that they do not run any applications that depend on graphflowx until it has been confirmed safe.

Conclusion

The graphflowx package has been identified as containing malicious code that compromises system security. Immediate action is required to uninstall the package and secure any sensitive information. Regular monitoring of dependencies is recommended to prevent future vulnerabilities.

See every vulnerability recorded for graphflowx →

Share this vulnerability

FAQ

Immediately uninstall the graphflowx package and rotate any sensitive information stored on your 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 needing to sign up.

No, there is currently no patched version available for the graphflowx package.

Failing to remove the package may result in unauthorized access to your system, leading to data breaches and potential loss of sensitive information.

While many npm packages are safe, it is essential to regularly monitor and audit your dependencies for vulnerabilities using tools like Vulert.

How To Fix

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

npm uninstall graphflowx

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.