Which versions of lbmtq7x are malicious?

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

How do I remediate lbmtq7x if I installed it?

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

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

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

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

Malicious package

lbmtq7xRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7937

Immediate action

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

gem uninstall lbmtq7x

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

cd964f457ea09c5957b8bfff6255eeb47202523aa8b75578091e6a991b04a8dc

d3beda15de3238022dc7e724ea105dde6f0cbaf48e2414f5903e257def2c60e6

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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