Critical Malicious Code Vulnerability in graph-dynamic Package

graph-dynamic Updated 03 Mar 2026

Summary

03/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1177: Malicious code in graph-dynamic (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The graph-dynamic package is an npm library designed for dynamic graph manipulation and visualization. It allows developers to create and manage graphs in a flexible manner, making it popular among data scientists and web developers. However, this package has been identified to contain malicious code, posing significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the graph-dynamic package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive data, including secrets and keys. The ramifications of this vulnerability are severe, as it can lead to complete control of the affected system by an external entity, making it critical for users to act swiftly.

How To Fix

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

npm uninstall graph-dynamic

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 this vulnerability other than removing the package and securing your system.

Conclusion

The graph-dynamic package has been identified as containing malicious code that can compromise systems. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for graph-dynamic →

Share this vulnerability

FAQ

You should remove the graph-dynamic package immediately and rotate any sensitive information stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Failure to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

Regularly monitor your dependencies using tools like Vulert and keep your packages updated to minimize the risk of vulnerabilities.

While removing the package is crucial, there is no guarantee that all malicious software has been removed. It is advisable to secure your system and rotate sensitive information.

How To Fix

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

npm uninstall graph-dynamic

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