Which versions of budmler are malicious?

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

How do I remediate budmler if I installed it?

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

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

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

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

Malicious package

budmlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in budmler (RubyGems)

MAL-2026-16778

Immediate action

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

gem uninstall budmler

Malicious versions

2 flagged

1.0.01.0.28587

Indicators of compromise (SHA-256)

7c845179e6699cd7b47effc972d26d67855bbca6af2aba702900f03a80438651

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07463

Credits

ReversingLabs · finder

Detect & block this

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