Which versions of bhmdler are malicious?

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

How do I remediate bhmdler if I installed it?

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

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

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

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

Malicious package

bhmdlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bhmdler (RubyGems)

MAL-2026-16588

Immediate action

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

gem uninstall bhmdler

Malicious versions

2 flagged

1.0.01.0.91234

Indicators of compromise (SHA-256)

207c319ae1fcbadca0a7a1911a82ad9e9b8af31c4d00bb1b393234ad763afffc

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07246

Credits

ReversingLabs · finder

Detect & block this

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