Which versions of lbrssudgaaoay are malicious?

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

How do I remediate lbrssudgaaoay if I installed it?

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

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

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

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

Malicious package

lbrssudgaaoayRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7949

Immediate action

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

gem uninstall lbrssudgaaoay

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7d130d68a4fbcc9104082794066b608411f846d04a15e880ae0228e3c48e7e02

9512d3eae10f2c64061f878a3bcd2731aacf3e279c3bc5ed9a061e697874924d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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