Which versions of buondler are malicious?

The following RubyGems versions of buondler are flagged malicious: 1.0.85690. Treat any of these as compromised.

How do I remediate buondler if I installed it?

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

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

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

Search your lockfiles and build artifacts for buondler (version 1.0.85690).

Malicious package

buondlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in buondler (RubyGems)

MAL-2026-17146

Immediate action

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

gem uninstall buondler

Malicious versions

1 flagged

1.0.85690

Indicators of compromise (SHA-256)

75c0bb5bd2ae706566b91b03e36017747a8f2277d3eb43ebcfd0df5cb7253230

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07835

Credits

ReversingLabs · finder

Detect & block this

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