Which versions of lbmtq3x are malicious?

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

How do I remediate lbmtq3x if I installed it?

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

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

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

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

Malicious package

lbmtq3xRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7933

Immediate action

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

gem uninstall lbmtq3x

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4a1ff445a84cc384e366460b357cc5679632ee7143751f1d48b1e75c87b9001f

617f8915783922efd2e57b8c3248e80acf452859f1201b288c91be95d509ef8c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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