Which versions of buodler are malicious?

The following RubyGems versions of buodler are flagged malicious: 1.0.92627. Treat any of these as compromised.

How do I remediate buodler if I installed it?

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

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

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

Search your lockfiles and build artifacts for buodler (version 1.0.92627).

Malicious package

buodlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in buodler (RubyGems)

MAL-2026-17142

Immediate action

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

gem uninstall buodler

Malicious versions

1 flagged

1.0.92627

Indicators of compromise (SHA-256)

5108155b69e199e601c55f9ac27b3be9d6885c4508a51b4810fe36d8dea986ec

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07831

Credits

ReversingLabs · finder

Detect & block this

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