Which versions of lbcaltestmvxcve are malicious?

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

How do I remediate lbcaltestmvxcve if I installed it?

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

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

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

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

Malicious package

lbcaltestmvxcveRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7910

Immediate action

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

gem uninstall lbcaltestmvxcve

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e4327aa0fb659b157aa758aba3b14eb920124507a529522a14255a3353572ca5

462c8f0c51c92afe2a3c109c6138f312b094a4e533afb3dd445d0ca0a38c6a1f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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