Which versions of bundrlef are malicious?

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

How do I remediate bundrlef if I installed it?

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

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

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

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

Malicious package

bundrlefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundrlef (RubyGems)

MAL-2026-17015

Immediate action

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

gem uninstall bundrlef

Malicious versions

2 flagged

1.0.01.0.42444

Indicators of compromise (SHA-256)

99e0d0c2c5fe584ababf6c5fe71f3787a41e903fabe3ea4f7d1db60c4f9ebc97

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07701

Credits

ReversingLabs · finder

Detect & block this

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