Which versions of lbcaltestywvidk are malicious?

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

How do I remediate lbcaltestywvidk if I installed it?

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

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

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

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

Malicious package

lbcaltestywvidkRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7913

Immediate action

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

gem uninstall lbcaltestywvidk

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ecfed213121e949bd037c59986cf248cad68689d2d998c9b6f91cd0dacad4cb9

3e216778ee8d72f9978f4005aa0bbfa41605482666d0e5d64d4433419aaf30e9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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