Malicious Code Detected in gem-client Package - MAL-2025-21255

gem-client Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21255: Malicious code in gem-client (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 gem-client package is a Node.js library designed for interacting with various gem-related functionalities. It is widely used in applications that require integration with gem services. However, this package has been identified to contain malicious code, posing significant security risks to applications utilizing it.

Vulnerability Detail

The vulnerability in the gem-client package originates from the inclusion of malicious code that can compromise the security of applications using this library. This malicious code can lead to unauthorized access, data breaches, and potential exploitation of the affected systems. The issue affects all versions starting from 0, making it critical 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 gem-client

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, consider removing the gem-client package from your project until a secure version is released. You can do this by executing the command: npm uninstall gem-client.

Conclusion

The gem-client package has been identified to contain malicious code, which poses significant risks to applications using it. Immediate action is required to update or remove the package to safeguard your systems. Utilize tools like Vulert to monitor for vulnerabilities effectively.

See every vulnerability recorded for gem-client →

Share this vulnerability

FAQ

The gem-client package is a Node.js library used for interacting with gem services, providing functionalities for applications that require gem integration.

The malicious code found in gem-client can lead to unauthorized access and data breaches, posing serious security risks to applications that rely on this package.

You can use Vulert, a tool that monitors and alerts for open-source vulnerabilities in your software. Simply upload your package-lock.json file to check for vulnerabilities.

If you cannot update the gem-client package right away, consider uninstalling it as a temporary measure to mitigate the risk until a secure version is available.

More information about this vulnerability can be found in the official GitHub repository and security advisories related to the gem-client package.

How To Fix

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

npm uninstall gem-client

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