Which versions of bundler-ruby are malicious?

The following RubyGems versions of bundler-ruby are flagged malicious: 1.0.88229. Treat any of these as compromised.

How do I remediate bundler-ruby if I installed it?

Remove bundler-ruby 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 bundler-ruby — how do I know if it already compromised me?

If bundler-ruby 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 bundler-ruby part of a known attack campaign?

Yes — bundler-ruby is associated with the RLMA-2026-07651 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 bundler-ruby across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bundler-ruby (version 1.0.88229).

Malicious package

bundler-rubyRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

bundler-ruby is a confirmed malicious RubyGems package (MAL-2026-16965) that executes malicious code on install (malicious version 1.0.88229). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bundler-ruby (RubyGems)

MAL-2026-16965

Immediate action

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

gem uninstall bundler-ruby

Malicious versions

1 flagged

1.0.88229

Indicators of compromise (SHA-256)

5b0195b173d4e241ed6a2ad7cc045dd3a4e87aed89072a64047fea55e02b9ee3

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for bundler-ruby (version 1.0.88229).
If you installed it — respond
Remove bundler-ruby 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 bundler-ruby 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. bundler-ruby on RubyGems has been identified as a malicious package (version 1.0.88229 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-07651

Credits

ReversingLabs · finder

Detect & block this

O3 blocks bundler-ruby-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