Which versions of bumdlea are malicious?

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

How do I remediate bumdlea if I installed it?

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

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

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

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

Malicious package

bumdleaRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bumdlea (RubyGems)

MAL-2026-16829

Immediate action

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

gem uninstall bumdlea

Malicious versions

2 flagged

1.0.01.0.79269

Indicators of compromise (SHA-256)

1969af8d753ffdde3202777f441daf7b73f2db6e9766bf8a7d03b9ae903bf0ab

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07515

Credits

ReversingLabs · finder

Detect & block this

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