Which versions of lbmtq2x are malicious?

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

How do I remediate lbmtq2x if I installed it?

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

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

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

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

Malicious package

lbmtq2xRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7932

Immediate action

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

gem uninstall lbmtq2x

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f034fe67a5d41b868b2c8f15152d909f457721512997a4d6b8ee78eb6f72cc29

098381f5f9facabe3581598af9abe2252d9c5e52d5b8150f0f752578eaafa5b8

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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