Which versions of lbrssebmlsaht are malicious?

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

How do I remediate lbrssebmlsaht if I installed it?

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

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

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

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

Malicious package

lbrssebmlsahtRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

lbrssebmlsaht is a confirmed malicious RubyGems package (MAL-2026-7944) 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 lbrssebmlsaht (RubyGems)

MAL-2026-7944

Immediate action

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

gem uninstall lbrssebmlsaht

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5247e1a41756d6c03a4ed93d5426246c8351f5086c86bd4e9bbb675025b811c9

46e0ac51176c995b4b450da097898a827d6bfca1b907d7125b6799613b5d3c30

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for lbrssebmlsaht (version 0.0.1).
If you installed it — respond
Remove lbrssebmlsaht 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 lbrssebmlsaht 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. lbrssebmlsaht 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-02595RLUA-2026-08412

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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