Which versions of lbcalxhogwjdqe are malicious?

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

How do I remediate lbcalxhogwjdqe if I installed it?

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

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

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

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

Malicious package

lbcalxhogwjdqeRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7919

Immediate action

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

gem uninstall lbcalxhogwjdqe

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7b1dfa711298f3b9df05801ca02e2f5bab051bc2da38a1cbc1b5d4b3fb55a102

6fdaf76f3efc61f7e2b804344cb93203141636b61cd60d95b255a85925a0a3ba

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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