Which versions of lbmtq5x are malicious?

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

How do I remediate lbmtq5x if I installed it?

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

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

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

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

Malicious package

lbmtq5xRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7935

Immediate action

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

gem uninstall lbmtq5x

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

81abed030e0a25b3ed5075e2fecc4ddd41b6e470753dfb3ec678a58c143aa3d1

0d5ca8d4c8698cce0c92d0a04a7c40d07d0fd7135a52f9a19fdc7db92d016376

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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