Which versions of lbrssyacvbhfoz are malicious?

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

How do I remediate lbrssyacvbhfoz if I installed it?

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

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

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

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

Malicious package

lbrssyacvbhfozRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7952

Immediate action

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

gem uninstall lbrssyacvbhfoz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e82ec1a07d99bb8c46321e28d9ed40e83cb996511eeb1a78e1e6960a55ae14f3

11ab6255422d6e12a15ba72ecbf51c69e629669b1f645095579904309e4a4d2b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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