Which versions of budler are malicious?

The following RubyGems versions of budler are flagged malicious: 1.0.60354, 1000.0.0. Treat any of these as compromised.

How do I remediate budler if I installed it?

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

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

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

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

Malicious package

budlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

budler is a confirmed malicious RubyGems package (MAL-2026-16777) that executes malicious code on install (malicious versions 1.0.60354, 1000.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in budler (RubyGems)

MAL-2026-16777

Immediate action

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

gem uninstall budler

Malicious versions

2 flagged

1.0.603541000.0.0

Indicators of compromise (SHA-256)

27b4cb705b3c2ad5a2e72e0ec8800bbcf7549ca064daf325398c433711379b15

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07462

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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