Critical Malicious Code Vulnerability in graphlib-js Package

graphlib-js Updated 17 Mar 2026

Summary

17/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1491: Malicious code in graphlib-js (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

graphlib-js is a JavaScript library that provides a way to create and manipulate directed graphs. It is commonly used in various applications for visualizing and managing relationships between data points. However, this package has been compromised, leading to significant security concerns for users who have it installed.

Vulnerability Detail

The vulnerability originates from malicious code embedded within the graphlib-js package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code is classified under CWE-506, indicating that it contains embedded malicious code that poses severe risks to system integrity and data security.

How To Fix

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

npm uninstall graphlib-js

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 posed by the malicious code in graphlib-js. The only recommended action is to uninstall the package and secure your system.

Conclusion

The graphlib-js package has been identified as containing malicious code that poses a significant security risk. Users are strongly advised to uninstall the package and secure their systems to prevent unauthorized access to sensitive information.

See every vulnerability recorded for graphlib-js →

Share this vulnerability

FAQ

graphlib-js is a JavaScript library used for creating and manipulating directed graphs, often utilized in data visualization and management applications.

The malicious code can compromise your system, allowing unauthorized access to sensitive information and potentially leading to data breaches.

You should immediately uninstall the graphlib-js package and rotate any sensitive information stored on your system.

As of now, there is no patched version available. Users are advised to remove the package entirely.

You can use Vulert to monitor and alert in real-time for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.

How To Fix

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

npm uninstall graphlib-js

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