Which versions of lbcaltestlredrf are malicious?

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

How do I remediate lbcaltestlredrf if I installed it?

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

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

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

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

Malicious package

lbcaltestlredrfRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7909

Immediate action

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

gem uninstall lbcaltestlredrf

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1ffc6c1ad7c62080ce7ece70977aad3ba1a775b956dbc9e52b1c46903777730e

1cc17120c15970d09faeb8453185ccaf9ec454b65ac5dcf6a9f04ec22da686c3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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