Which versions of lbmtq11x are malicious?

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

How do I remediate lbmtq11x if I installed it?

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

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

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

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

Malicious package

lbmtq11xRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7930

Immediate action

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

gem uninstall lbmtq11x

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f3b89050c22e76171d32102518b4f85f5914fa97bb7b9dbc40053ebbc24221e0

2aa5d05c886d337212ccabee728a583420abf3fb9707fa8542b848b8eca62a77

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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