Which versions of bumdlrer are malicious?

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

How do I remediate bumdlrer if I installed it?

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

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

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

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

Malicious package

bumdlrerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bumdlrer (RubyGems)

MAL-2026-16865

Immediate action

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

gem uninstall bumdlrer

Malicious versions

2 flagged

1.0.01.0.53888

Indicators of compromise (SHA-256)

c759fe73078ccc4664a507d9f9caf5d3a64ae62124c4a2c43f1da8fc334ea167

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07551

Credits

ReversingLabs · finder

Detect & block this

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