Which versions of lbrssyjzqfxbul are malicious?

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

How do I remediate lbrssyjzqfxbul if I installed it?

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

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

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

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

Malicious package

lbrssyjzqfxbulRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7955

Immediate action

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

gem uninstall lbrssyjzqfxbul

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3260f6aa47f1e5785a93f9504964e4f5ece6c150aa996b130600041216f1a933

5b3407dafdb95491d732d195ed7b6bf339f43eb5081fa055fa17586f1b036ad3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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