Which versions of bemdler are malicious?

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

How do I remediate bemdler if I installed it?

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

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

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

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

Malicious package

bemdlerRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bemdler (RubyGems)

MAL-2026-16578

Immediate action

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

gem uninstall bemdler

Malicious versions

2 flagged

1.0.01.0.84342

Indicators of compromise (SHA-256)

d17a7a2b55db4956988aa7bec5e2ad3c9540ec51f1ffc8b95d986597d358c9d8

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07231

Credits

ReversingLabs · finder

Detect & block this

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