Malicious Code Detected in gmx-subgraph Package

gmx-subgraph Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21612: Malicious code in gmx-subgraph (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 gmx-subgraph package is an npm library designed for interacting with the GMX decentralized exchange's subgraph. It provides developers with tools to access and manipulate data related to trading activities, liquidity pools, and other functionalities of the GMX platform. However, recent findings have revealed that this package contains malicious code, posing significant risks to users and their applications.

Vulnerability Detail

The vulnerability in the gmx-subgraph package stems from the inclusion of malicious code that can compromise the security of applications utilizing this library. This code may allow unauthorized access to sensitive data, facilitate data manipulation, or enable other harmful activities. 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 gmx-subgraph

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

As a temporary workaround, users are advised to remove the gmx-subgraph package from their projects until a secure version is released. This can be done using the command: npm uninstall gmx-subgraph. Consider using alternative packages that provide similar functionalities without the associated risks.

Conclusion

The discovery of malicious code in the gmx-subgraph package highlights the importance of vigilance in managing open-source dependencies. Users are urged to take immediate action by updating or removing the affected package to safeguard their applications from potential threats.

See every vulnerability recorded for gmx-subgraph →

Share this vulnerability

FAQ

The gmx-subgraph package is an npm library that allows developers to interact with the GMX decentralized exchange's subgraph, providing access to trading and liquidity data.

The malicious code found in the gmx-subgraph package can compromise application security, potentially allowing unauthorized access to sensitive information or enabling harmful activities.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. By analyzing your package-lock.json file, it can identify if your application is affected by the gmx-subgraph vulnerability.

As of now, a patch has not been released. Users should monitor the official repository for updates and apply the patch as soon as it becomes available.

If removal is not an option, consider isolating the package's functionality and implementing strict security measures to mitigate potential risks until a secure version is released.

How To Fix

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

npm uninstall gmx-subgraph

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