Which versions of lbrssyrofhwlco are malicious?

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

How do I remediate lbrssyrofhwlco if I installed it?

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

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

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

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

Malicious package

lbrssyrofhwlcoRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7957

Immediate action

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

gem uninstall lbrssyrofhwlco

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1661cab9ac7730631d2d144f5cc8243dce6ea0ee0288ff89c5129bc34a09a32a

e40057383af6d1983abb0b24cd3fe048d96fe269c0413742ed312b7d8b1d6115

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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