Which versions of buadlef are malicious?

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

How do I remediate buadlef if I installed it?

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

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

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

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

Malicious package

buadlefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in buadlef (RubyGems)

MAL-2026-16765

Immediate action

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

gem uninstall buadlef

Malicious versions

2 flagged

1.0.01.0.41912

Indicators of compromise (SHA-256)

17cc5cdb7825569e656055bce7ad5505f901f6fe5dac1377a5a4cd4e77aebe53

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07450

Credits

ReversingLabs · finder

Detect & block this

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