Which versions of lbcaltestyoeaua are malicious?

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

How do I remediate lbcaltestyoeaua if I installed it?

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

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

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

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

Malicious package

lbcaltestyoeauaRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7912

Immediate action

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

gem uninstall lbcaltestyoeaua

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3816ad6b093a3bd25006f8fdd193e432579f65bcc6d100b9a4fd54a5afff5b68

88546a5da0e8ed0130ac5ad160b78a4894b28040f1b0ace0d06611bb16e77184

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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