Which versions of lbrssvvqzexsn are malicious?

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

How do I remediate lbrssvvqzexsn if I installed it?

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

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

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

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

Malicious package

lbrssvvqzexsnRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7951

Immediate action

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

gem uninstall lbrssvvqzexsn

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c8995eb8aec823eec3252242cf71b31f72b285ca732a6cf010598826030ba741

61dbc07eedd1433f8ecf04303f2eaba9ed6675762e94e71eb85cbaff7a254b87

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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