Which versions of lbcalxcnrlgidi are malicious?

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

How do I remediate lbcalxcnrlgidi if I installed it?

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

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

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

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

Malicious package

lbcalxcnrlgidiRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7915

Immediate action

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

gem uninstall lbcalxcnrlgidi

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3d8cdb4aac9d5db1a399e13993640fe7b45cbab9ab77c9184059d62047aa4aa1

c0799690067e8ec2108c454f1ddc0baecf359c1bc7a760d68d94e3c812ac3db2

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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