Which versions of bunodlef are malicious?

The following RubyGems versions of bunodlef are flagged malicious: 1.0.54605. Treat any of these as compromised.

How do I remediate bunodlef if I installed it?

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

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

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

Search your lockfiles and build artifacts for bunodlef (version 1.0.54605).

Malicious package

bunodlefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bunodlef (RubyGems)

MAL-2026-17108

Immediate action

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

gem uninstall bunodlef

Malicious versions

1 flagged

1.0.54605

Indicators of compromise (SHA-256)

af54a476b0e2460107972cbdb3d8d74a6acf2701a24a6e1194963e526da9712d

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07794

Credits

ReversingLabs · finder

Detect & block this

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