Which versions of lbcaltestljjirx are malicious?

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

How do I remediate lbcaltestljjirx if I installed it?

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

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

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

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

Malicious package

lbcaltestljjirxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7908

Immediate action

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

gem uninstall lbcaltestljjirx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7eb5928b0c6de72a967b4b00552274e0188eb8494c7201cbfcfa502c200f16c2

d7e0eb2623feaf7bf26dbab0891d566951dfae6236595eca4d308cbf5af59bbd

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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