Which versions of lbeng658 are malicious?

The following RubyGems versions of lbeng658 are flagged malicious: 0.0.70658. Treat any of these as compromised.

How do I remediate lbeng658 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lbeng658 (version 0.0.70658).

Malicious package

lbeng658RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

lbeng658 is a confirmed malicious RubyGems package (MAL-2026-7922) that executes malicious code on install (malicious version 0.0.70658). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lbeng658 (RubyGems)

MAL-2026-7922

Immediate action

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

gem uninstall lbeng658

Malicious versions

1 flagged

0.0.70658

Indicators of compromise (SHA-256)

4d136dc85ecc3b88d55fab389d48375fdc156bf76692b46eddd34d6c70972c09

bed8d895145a1588a23ccae4729b65f92304bb8f6325249a12a6c231ffc41bad

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02573RLUA-2026-08390

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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