Which versions of lbmtq10x are malicious?

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

How do I remediate lbmtq10x if I installed it?

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

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

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

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

Malicious package

lbmtq10xRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7929

Immediate action

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

gem uninstall lbmtq10x

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

90c750e62412670d28de3a3ac3b5b4a80e88f158cac3bf806e2972445bb790c0

e29035f28afab67b65a4dd29fe9e7cc2a6470836b378f12db5d199c4c54284c4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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