Which versions of bumdller are malicious?

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

How do I remediate bumdller if I installed it?

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

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

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

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

Malicious package

bumdllerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bumdller (RubyGems)

MAL-2026-16859

Immediate action

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

gem uninstall bumdller

Malicious versions

2 flagged

1.0.01.0.15074

Indicators of compromise (SHA-256)

6fb0e61deaabfd3a049b25bacbd26561aed488dbf003de057a1cd161f97a0685

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07545

Credits

ReversingLabs · finder

Detect & block this

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