Which versions of bumduer are malicious?

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

How do I remediate bumduer if I installed it?

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

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

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

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

Malicious package

bumduerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bumduer (RubyGems)

MAL-2026-16877

Immediate action

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

gem uninstall bumduer

Malicious versions

2 flagged

1.0.01.0.5701

Indicators of compromise (SHA-256)

a687a2c5ae9ce82adf6d951388e64f2214969db3ec1bce9ae4cadb91275e5f60

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07563

Credits

ReversingLabs · finder

Detect & block this

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