Which versions of bumdlei are malicious?

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

How do I remediate bumdlei if I installed it?

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

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

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

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

Malicious package

bumdleiRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bumdlei (RubyGems)

MAL-2026-16835

Immediate action

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

gem uninstall bumdlei

Malicious versions

2 flagged

1.0.01.0.49724

Indicators of compromise (SHA-256)

a65d9f80456bbf38e5811991b1ab56fb84776a4dba6b4989d93f284c60bf7f0a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07521

Credits

ReversingLabs · finder

Detect & block this

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