Which versions of lbrssysrtydeaa are malicious?

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

How do I remediate lbrssysrtydeaa if I installed it?

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

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

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

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

Malicious package

lbrssysrtydeaaRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7958

Immediate action

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

gem uninstall lbrssysrtydeaa

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e905a70735342fc01338426f76d35622184fdb1cee414489e6bba4afb2e6f370

f428cf1bd5101a9c8d37c3a1aada3af6980dbe0c8a824f60f8f6182fa2b50c5d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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