Which versions of plugin-gem-example are malicious?

The following RubyGems versions of plugin-gem-example are flagged malicious: 99.99.99, 100.9.9. Treat any of these as compromised.

How do I remediate plugin-gem-example if I installed it?

Remove plugin-gem-example from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed plugin-gem-example — how do I know if it already compromised me?

If plugin-gem-example was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is plugin-gem-example part of a known attack campaign?

Yes — plugin-gem-example is associated with the RLMA-2026-01692, RLUA-2026-08949 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find plugin-gem-example across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for plugin-gem-example (2 malicious versions).

Malicious package

plugin-gem-exampleRubyGems

Advisory published Mar 24, 2026Updated Sep 24, 2026

plugin-gem-example is a confirmed malicious RubyGems package (MAL-2026-2402) that executes malicious code on install (malicious versions 99.99.99, 100.9.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in plugin-gem-example (RubyGems)

MAL-2026-2402

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

gem uninstall plugin-gem-example

Malicious versions

2 flagged

99.99.99100.9.9

Indicators of compromise (SHA-256)

7a99d094da7a66199dd2041d12901340335cbca2bf0f677f50d5493b8a6006f2

91811de6752879a88d98111e715fcc7fb9628fdac6013ed30c856aae56175c0c

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for plugin-gem-example (2 malicious versions).
If you installed it — respond
Remove plugin-gem-example from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If plugin-gem-example was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. plugin-gem-example on RubyGems has been identified as a malicious package (versions 99.99.99, 100.9.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01692RLUA-2026-08949

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks plugin-gem-example-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database