Which versions of lbmtq6x are malicious?

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

How do I remediate lbmtq6x if I installed it?

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

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

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

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

Malicious package

lbmtq6xRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7936

Immediate action

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

gem uninstall lbmtq6x

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

38bcd6e89e16a2086c97c41496f26042ae5bbda0c0f14de8967a7f63aa25d744

eb441699b6d019b2ea0e0a31cc23acc1613b26dc03d148dc4ab7902ce7bf622c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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