Which versions of lbcaltestcczorx are malicious?

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

How do I remediate lbcaltestcczorx if I installed it?

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

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

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

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

Malicious package

lbcaltestcczorxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7904

Immediate action

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

gem uninstall lbcaltestcczorx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ee153dd279dbbd8dfc95e526cfba80998e5464b52d700aa49148acd6b4b0db78

b43ce71609163708cc9effd88c7f823c60457dacb426e777f9028ab07cf146ab

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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