Which versions of lbqtcccksw are malicious?

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

How do I remediate lbqtcccksw if I installed it?

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

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

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

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

Malicious package

lbqtccckswRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7942

Immediate action

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

gem uninstall lbqtcccksw

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

295707c71c7ea120e63b34f7f7fe022af9a29d7fb0e4dcf6d866bd863796ec35

3bd7fadcdc9ac48c13703d997260e53d530b4c542d63bd7e7b973bb6d0909f58

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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