Malicious Code Detected in eazegraph Package - Security Alert
Summary
MAL-2025-19100: Malicious code in eazegraph (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The eazegraph package is an npm library designed for graphing and data visualization, offering users a range of functionalities to create interactive and dynamic graphs. However, recent findings have revealed that this package contains malicious code, posing significant security risks to users and their applications.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the eazegraph package. This code can potentially compromise user data, lead to unauthorized access, and disrupt application functionality. The issue was introduced in version 0 and affects all subsequent versions, making it critical for users to address this vulnerability promptly.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall eazegraphIf 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
As a temporary workaround, users are advised to remove the eazegraph package from their projects until a secure version is released. This can be done using the command: 'npm uninstall eazegraph'.
Conclusion
The eazegraph package has been identified to contain malicious code, posing serious security threats to users. It is essential to update or remove the package to safeguard your applications. Regular monitoring for updates and vulnerabilities is recommended.
See every vulnerability recorded for eazegraph →
FAQ
eazegraph is an npm package used for creating graphs and data visualizations in web applications.
The specific nature of the malicious code has not been disclosed, but it poses risks such as data theft and unauthorized access.
You can use Vulert, which monitors open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.
Currently, there is no specific patch mentioned. Users should monitor the package repository for updates.
If immediate updates are not possible, consider removing the package from your project as a temporary measure.
