Which versions of bundlerl are malicious?

The following RubyGems versions of bundlerl are flagged malicious: 1.0.0, 1.0.92832. Treat any of these as compromised.

How do I remediate bundlerl if I installed it?

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

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

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

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

Malicious package

bundlerlRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

bundlerl is a confirmed malicious RubyGems package (MAL-2026-16970) that executes malicious code on install (malicious versions 1.0.0, 1.0.92832). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bundlerl (RubyGems)

MAL-2026-16970

Immediate action

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

gem uninstall bundlerl

Malicious versions

2 flagged

1.0.01.0.92832

Indicators of compromise (SHA-256)

2b74cc679aa203884cd327bc42332ce65bdf2ac9eb2336e4b653f2f8d3f85054

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07656

Credits

ReversingLabs · finder

Detect & block this

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