Which versions of bendlef are malicious?

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

How do I remediate bendlef if I installed it?

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

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

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

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

Malicious package

bendlefRubyGems

Advisory published Sep 22, 2026Updated Sep 24, 2026

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

Malicious code in bendlef (RubyGems)

MAL-2026-16579

Immediate action

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

gem uninstall bendlef

Malicious versions

2 flagged

1.0.01.0.81185

Indicators of compromise (SHA-256)

588f23c2f1335654c8d9968d900a9d1b9f13ed71700bc8ebf4373df8db7aefc2

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-07233

Credits

ReversingLabs · finder

Detect & block this

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