Which versions of lbrssmmqrwkvm are malicious?

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

How do I remediate lbrssmmqrwkvm if I installed it?

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

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

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

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

Malicious package

lbrssmmqrwkvmRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7948

Immediate action

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

gem uninstall lbrssmmqrwkvm

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4e333e3e80ab9403908b241c529c116d6d9708e216daae9f3ea30cc3282c1c27

ffb2439d6c7118c86110218b84bd8ac45a76793e302bd63847dd517e88a79125

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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