Which versions of lmbp24941 are malicious?

The following RubyGems versions of lmbp24941 are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate lmbp24941 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lmbp24941 (version 0.0.1).

Malicious package

lmbp24941RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lmbp24941 (RubyGems)

MAL-2026-8023

Immediate action

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

gem uninstall lmbp24941

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b424cde832551c43f829b6d818d602fdbc22d177aad8f83694a81e4f4ba9767c

7f091f4a8737de2cc940449a97c2f56a790477c2325fd2e09130afb62f86d160

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02674RLUA-2026-08509

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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