Which versions of lbcalxagpsupya are malicious?

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

How do I remediate lbcalxagpsupya if I installed it?

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

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

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

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

Malicious package

lbcalxagpsupyaRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7914

Immediate action

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

gem uninstall lbcalxagpsupya

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e60551e4203bda8ca78fcb90d2dd37463ae39c70140fb0b0fe180a53392a02aa

8d994e36952cf818abb6635bdd0e2d703510dfe3968006bfb3b5b0b4fca2d7b3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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