Which versions of bumdoer are malicious?

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

How do I remediate bumdoer if I installed it?

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

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

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

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

Malicious package

bumdoerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bumdoer (RubyGems)

MAL-2026-16872

Immediate action

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

gem uninstall bumdoer

Malicious versions

2 flagged

1.0.01.0.79467

Indicators of compromise (SHA-256)

bec3f867e564e4499d8bd0f9f293a4dda2a4a1bdad0182aeb0360be2282dcf83

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07558

Credits

ReversingLabs · finder

Detect & block this

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