Which versions of lbmtq8x are malicious?

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

How do I remediate lbmtq8x if I installed it?

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

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

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

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

Malicious package

lbmtq8xRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7938

Immediate action

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

gem uninstall lbmtq8x

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

88971eb956a671d01c326579ab8bfb51926892bc6964d16b5d58fbfeac854f4a

cbdc0918ab1aeb82c93da1516cc5a6c2fd1b9ed368fd3ac94bcfd2c2b7540f99

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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