Which versions of lbrsseyuqeyzf are malicious?

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

How do I remediate lbrsseyuqeyzf if I installed it?

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

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

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

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

Malicious package

lbrsseyuqeyzfRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7945

Immediate action

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

gem uninstall lbrsseyuqeyzf

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4c2f01d87fe5b4f97e0ac1b375876f8332a90ba9f1766c764bfdcb950aacc32b

cc12d3b072068d7959c51584f4a42ffba687cf9c2351f187a573f167b2c8ec49

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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