Which versions of lbrssyjsxxubbr are malicious?

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

How do I remediate lbrssyjsxxubbr if I installed it?

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

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

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

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

Malicious package

lbrssyjsxxubbrRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7954

Immediate action

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

gem uninstall lbrssyjsxxubbr

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

cb3119756614930fa76c5ff834ca62f6dbadbd098895e3aec7cb14af4881a5d9

253e06a556689baa56a642b415c6db71cdac1e8e8d6b8860dca605b915b6534c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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