Which versions of lbcaltestrlmcpe are malicious?

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

How do I remediate lbcaltestrlmcpe if I installed it?

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

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

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

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

Malicious package

lbcaltestrlmcpeRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7911

Immediate action

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

gem uninstall lbcaltestrlmcpe

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

406812f8d094b79740775c6f70377bda7ab5da46631d4e2e6c92cd5183f87986

455b250855bda0e446443199976cab51398c45ae44f995fb4540cd04697c72f8

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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