Which versions of bumdleir are malicious?

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

How do I remediate bumdleir if I installed it?

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

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

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

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

Malicious package

bumdleirRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bumdleir (RubyGems)

MAL-2026-16836

Immediate action

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

gem uninstall bumdleir

Malicious versions

2 flagged

1.0.01.0.35887

Indicators of compromise (SHA-256)

12c13b8437356b768f44ea2c72a7246d3629fa14c8db15f54447fca2dbd09cc5

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07522

Credits

ReversingLabs · finder

Detect & block this

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