Which versions of lbmtq9x are malicious?

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

How do I remediate lbmtq9x if I installed it?

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

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

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

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

Malicious package

lbmtq9xRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7939

Immediate action

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

gem uninstall lbmtq9x

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7d482935d4cc5d9ff9ae1f1b0066cd680fcf946978d316175efbb31747fcf488

7984c1e566e7d1a6f09fe61fc783fd40ceb22222406709a520857c30f710393e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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