Which versions of bumrler are malicious?

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

How do I remediate bumrler if I installed it?

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

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

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

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

Malicious package

bumrlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bumrler (RubyGems)

MAL-2026-16891

Immediate action

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

gem uninstall bumrler

Malicious versions

2 flagged

1.0.01.0.57453

Indicators of compromise (SHA-256)

67186ec96590ec8c734df9b4bc9bf953a1a43c3f44970e2a2dd0ce286cdcc30c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07577

Credits

ReversingLabs · finder

Detect & block this

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