Which versions of lbcalxhayqouyj are malicious?

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

How do I remediate lbcalxhayqouyj if I installed it?

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

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

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

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

Malicious package

lbcalxhayqouyjRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7918

Immediate action

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

gem uninstall lbcalxhayqouyj

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f95146a12bc3c4bb993eedebc90424ee124b56ac1d39a578a611af9b228dc482

29ab25d6f1b4d71e252b180a1d55cdda54aca73c3ca1608b209848d08ec6d08b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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