Which versions of buedlef are malicious?

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

How do I remediate buedlef if I installed it?

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

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

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

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

Malicious package

buedlefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in buedlef (RubyGems)

MAL-2026-16782

Immediate action

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

gem uninstall buedlef

Malicious versions

2 flagged

1.0.01.0.82457

Indicators of compromise (SHA-256)

26d3c752c97991a2d2cab374d07c482fc6b6310961459513a6b793137645b8f7

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07467

Credits

ReversingLabs · finder

Detect & block this

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