Which versions of lboaktdmwa are malicious?

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

How do I remediate lboaktdmwa if I installed it?

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

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

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

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

Malicious package

lboaktdmwaRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7941

Immediate action

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

gem uninstall lboaktdmwa

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

578cba3ca765b94579a03ccac3c7b1e4c0305c0cd0b769660b7c80be54a1f8a2

4b5447bd37b20e233e7c7b21f7e3997e38c7d822953f7d4368e4bfd330ab3079

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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