Which versions of bundler-rb are malicious?

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

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

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

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

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

Search your lockfiles and build artifacts for bundler-rb (version 1.0.39010).

Malicious package

bundler-rbRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundler-rb (RubyGems)

MAL-2026-16964

Immediate action

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

gem uninstall bundler-rb

Malicious versions

1 flagged

1.0.39010

Indicators of compromise (SHA-256)

0760167686c70390886fae4a1af0fcd497b933d6c00a87c06791b287e66bc81a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07650

Credits

ReversingLabs · finder

Detect & block this

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