Critical Malicious Code Vulnerability in plugin-gem-example Package

plugin-gem-example Updated 01 Apr 2026

Summary

24/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-2402: Malicious code in plugin-gem-example (RubyGems). Affects plugin-gem-example versions 100.9.9 – 99.99.99. 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 plugin-gem-example package is a RubyGem designed to facilitate plugin development for Ruby applications. It provides developers with essential tools and libraries to create and manage plugins efficiently. However, this package has been identified as containing malicious code, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the plugin-gem-example package. This code can compromise the security of applications that depend on it, potentially leading to unauthorized access, data breaches, or system manipulation. The malicious code was identified in versions 99.99.99 and 100.9.9, and it is crucial for developers to be aware of the risks associated with using this package.

How To Fix

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

bundle remove plugin-gem-example

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, developers can remove the plugin-gem-example package from their projects until a secure version is confirmed. This can be done using the command: 'gem uninstall plugin-gem-example'.

Conclusion

The plugin-gem-example package has been identified as containing malicious code, posing serious security risks to applications that utilize it. Developers are urged to update or remove the package to safeguard their applications. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in real-time.

See every vulnerability recorded for plugin-gem-example →

Share this vulnerability

FAQ

The malicious code can lead to unauthorized access and potential data breaches in applications that use the package.

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

Versions 99.99.99 and 100.9.9 of the plugin-gem-example package are known to contain the malicious code.

Yes, you can temporarily uninstall the plugin-gem-example package until a secure version is released.

The vulnerability was reported by ReversingLabs, a cybersecurity firm specializing in threat detection.

How To Fix

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

bundle remove plugin-gem-example

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