Which versions of bundnlef are malicious?

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

How do I remediate bundnlef if I installed it?

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

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

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

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

Malicious package

bundnlefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bundnlef (RubyGems)

MAL-2026-17007

Immediate action

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

gem uninstall bundnlef

Malicious versions

2 flagged

1.0.01.0.36235

Indicators of compromise (SHA-256)

21006436508430190192f59a37de014ff68049c479a62b277a25cbea726769d4

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07693

Credits

ReversingLabs · finder

Detect & block this

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