Which versions of bumdled are malicious?

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

How do I remediate bumdled if I installed it?

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

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

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

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

Malicious package

bumdledRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bumdled (RubyGems)

MAL-2026-16831

Immediate action

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

gem uninstall bumdled

Malicious versions

2 flagged

1.0.01.0.55997

Indicators of compromise (SHA-256)

dec506f0c7662809db32c739f3292efb4ee8b8558e42b914003317d7ab3c6f25

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07517

Credits

ReversingLabs · finder

Detect & block this

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