Which versions of bundlerr are malicious?

The following RubyGems versions of bundlerr are flagged malicious: 1.0.15959, 1000.0.0. Treat any of these as compromised.

How do I remediate bundlerr if I installed it?

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

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

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

Search your lockfiles and build artifacts for bundlerr (2 malicious versions).

Malicious package

bundlerrRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

bundlerr is a confirmed malicious RubyGems package (MAL-2026-16973) that executes malicious code on install (malicious versions 1.0.15959, 1000.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bundlerr (RubyGems)

MAL-2026-16973

Immediate action

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

gem uninstall bundlerr

Malicious versions

2 flagged

1.0.159591000.0.0

Indicators of compromise (SHA-256)

c06168eb2e281136dc261d6b8578aed7a0e81c1154434ece517f20d33bbd85d8

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07659

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks bundlerr-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