Which versions of bumdlr are malicious?

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

How do I remediate bumdlr if I installed it?

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

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

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

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

Malicious package

bumdlrRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bumdlr (RubyGems)

MAL-2026-16863

Immediate action

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

gem uninstall bumdlr

Malicious versions

2 flagged

1.0.01.0.71801

Indicators of compromise (SHA-256)

2523b59ad2f26ad75aacea661bb84babf7600b8d14b300d198735561ba440442

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07549

Credits

ReversingLabs · finder

Detect & block this

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