Which versions of bmdler are malicious?

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

How do I remediate bmdler if I installed it?

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

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

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

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

Malicious package

bmdlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bmdler (RubyGems)

MAL-2026-16729

Immediate action

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

gem uninstall bmdler

Malicious versions

2 flagged

1.0.01.0.64535

Indicators of compromise (SHA-256)

31662b436bbc2e51fceda1cd5b7d2e7df4fc9bf1e13d3b5d81f7603c5751bd65

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07397

Credits

ReversingLabs · finder

Detect & block this

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