Which versions of bumsler are malicious?

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

How do I remediate bumsler if I installed it?

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

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

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

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

Malicious package

bumslerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bumsler (RubyGems)

MAL-2026-16893

Immediate action

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

gem uninstall bumsler

Malicious versions

2 flagged

1.0.01.0.79291

Indicators of compromise (SHA-256)

31c9c586e419a9be1bcc7d65a06db8ad02150a774bd2a71f5457252583422aa9

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07579

Credits

ReversingLabs · finder

Detect & block this

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