Malicious Code Detected in gmxlib: A Critical Security Concern

gmxlib Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21614: Malicious code in gmxlib (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

gmxlib is an npm package designed for developers to facilitate various functionalities within their applications. It is widely used due to its ease of integration and robust features. However, recent findings have revealed that this package contains malicious code, posing significant security risks to applications that utilize it.

Vulnerability Detail

The vulnerability in gmxlib stems from the inclusion of malicious code within the package. This code can potentially compromise the security of applications that depend on gmxlib, leading to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions, making it imperative for users to take immediate action.

How To Fix

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

npm uninstall gmxlib

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 measure, consider removing gmxlib from your project until a secure version is released. You can do this by executing: npm uninstall gmxlib. Additionally, review your project's dependencies to identify any other potentially vulnerable packages.

Conclusion

The discovery of malicious code in gmxlib presents a serious security threat to applications that utilize this package. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications. Regular monitoring of dependencies using tools like Vulert can help maintain security in your projects.

See every vulnerability recorded for gmxlib →

Share this vulnerability

FAQ

gmxlib is an npm package used for various functionalities in JavaScript applications, but it has recently been found to contain malicious code.

The malicious code was identified by security researchers from Amazon Inspector, who reported it as part of their vulnerability findings.

Using gmxlib with the malicious code can lead to unauthorized access, data breaches, and other security vulnerabilities in your application.

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 requiring any signup.

If an immediate update is not possible, consider removing gmxlib from your project as a temporary workaround 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 gmxlib

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