Which versions of bnudlef are malicious?

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

How do I remediate bnudlef if I installed it?

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

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

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

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

Malicious package

bnudlefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bnudlef (RubyGems)

MAL-2026-16734

Immediate action

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

gem uninstall bnudlef

Malicious versions

2 flagged

1.0.01.0.53800

Indicators of compromise (SHA-256)

a7c197e72102db434e19c59dd4db9f9d9e781641d62f26c125cd96905894cc80

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07402

Credits

ReversingLabs · finder

Detect & block this

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