Which versions of lbwmttmkfk are malicious?

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

How do I remediate lbwmttmkfk if I installed it?

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

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

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

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

Malicious package

lbwmttmkfkRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7962

Immediate action

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

gem uninstall lbwmttmkfk

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b7a5fe75da76741b5d8fd377896058c8f5e537a9da9e79f5ccf4fd8c7eb72f66

1c2bf8b821308954af2c44fd3d182352b511978c9652b3048b40f538b335fdc6

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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