Which versions of buhdlef are malicious?

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

How do I remediate buhdlef if I installed it?

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

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

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

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

Malicious package

buhdlefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in buhdlef (RubyGems)

MAL-2026-16790

Immediate action

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

gem uninstall buhdlef

Malicious versions

2 flagged

1.0.01.0.93541

Indicators of compromise (SHA-256)

48ec231de0f2e4c09cdb74ed9709cc4ddc9307fd4d80c9af84a1bb31e34e6baf

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07475

Credits

ReversingLabs · finder

Detect & block this

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