Which versions of lbcalxeyndhbdj are malicious?

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

How do I remediate lbcalxeyndhbdj if I installed it?

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

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

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

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

Malicious package

lbcalxeyndhbdjRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7917

Immediate action

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

gem uninstall lbcalxeyndhbdj

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

547560d3e97e9b0f7952e58f5708b8642d8ef8bdaf2e92e82799285f7bf5bd7e

0292bbd191235adedce13fcc41413e92ff4a52f8c87a220e93722dfb5c5a2deb

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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