Which versions of lbmtq1x are malicious?

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

How do I remediate lbmtq1x if I installed it?

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

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

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

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

Malicious package

lbmtq1xRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7931

Immediate action

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

gem uninstall lbmtq1x

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5040ab493a4b9eb833800153da40122d95094aeb5cf21ba4bf548cc1a0cb9fb6

7483662360e5d8e5cea6150adc53523106613b8efb8da7d2b09b6132dad6da01

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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