Which versions of buondlef are malicious?

The following RubyGems versions of buondlef are flagged malicious: 1.0.14096. Treat any of these as compromised.

How do I remediate buondlef if I installed it?

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

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

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

Search your lockfiles and build artifacts for buondlef (version 1.0.14096).

Malicious package

buondlefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in buondlef (RubyGems)

MAL-2026-17145

Immediate action

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

gem uninstall buondlef

Malicious versions

1 flagged

1.0.14096

Indicators of compromise (SHA-256)

1ac7d6fe80183545b7042bfa1f5bde27ffffbceb3a2cf9c9879a7ccde55b30ab

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07834

Credits

ReversingLabs · finder

Detect & block this

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