Which versions of benlder are malicious?

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

How do I remediate benlder if I installed it?

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

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

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

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

Malicious package

benlderRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in benlder (RubyGems)

MAL-2026-16581

Immediate action

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

gem uninstall benlder

Malicious versions

2 flagged

1.0.01.0.1940

Indicators of compromise (SHA-256)

3e37277f22cd739bfb559f1aa0b481031f36fb4991fe613055140247abcae2cf

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07236

Credits

ReversingLabs · finder

Detect & block this

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