Malicious Code Detected in gemjacker: A Critical npm Vulnerability

gemjacker Updated 02 Oct 2025

Summary

14/08/2025
CRITICAL
No i
Critical
Not published

MAL-2025-21259: Malicious code in gemjacker (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

The gemjacker package is an npm library designed to facilitate the management and manipulation of Ruby gems within JavaScript environments. It is often utilized by developers who require seamless integration between Ruby and JavaScript ecosystems. However, this package has been identified to contain malicious code, posing significant risks to applications that rely on it.

Vulnerability Detail

The vulnerability in the gemjacker package stems from the presence of malicious code that can compromise the security of applications using this library. This code may lead to unauthorized access, data breaches, or other harmful actions within the affected systems. The malicious nature of this code was confirmed by security researchers, highlighting the importance of immediate action to mitigate potential damage.

How To Fix

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

npm uninstall gemjacker

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, you may consider removing the gemjacker package from your project until a secure version is released. This can be done using the command: 'npm uninstall gemjacker'. Additionally, review your codebase for any dependencies that may rely on this package and assess their impact.

Conclusion

The discovery of malicious code in the gemjacker npm package poses a serious threat to applications that utilize it. Immediate action is required to update or remove the package to protect your systems from potential vulnerabilities. Utilizing tools like Vulert can help monitor and manage these risks effectively.

See every vulnerability recorded for gemjacker →

Share this vulnerability

FAQ

Gemjacker is an npm package that allows developers to manage Ruby gems within JavaScript applications.

The malicious code in gemjacker can lead to unauthorized access and potential data breaches in applications using this library.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.

It is recommended to check the gemjacker repository for any updates or patches that address the malicious code issue.

As a temporary measure, consider uninstalling the gemjacker package and reviewing your dependencies to mitigate risks.

How To Fix

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

npm uninstall gemjacker

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