Which versions of lbrssuuxosyfo are malicious?

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

How do I remediate lbrssuuxosyfo if I installed it?

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

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

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

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

Malicious package

lbrssuuxosyfoRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7950

Immediate action

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

gem uninstall lbrssuuxosyfo

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2440afbb3a917a64518d92cf7bd814bc70f112e278d0f15032ab15d81f61c949

6dd0fddf40924792f5af3ea5050abcedaee6aed4b33c524d840c313122aa182b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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