Which versions of lczbvghwyxk are malicious?

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

How do I remediate lczbvghwyxk if I installed it?

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

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

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

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

Malicious package

lczbvghwyxkRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7988

Immediate action

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

gem uninstall lczbvghwyxk

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b9cc20068cf79902aefd912f30c6610e5080bed0330fe2a2bd1fcc7430365c1a

cac23d196527e8cfcadc57cfa0481291facd2a11f1734ac3c243c3834555c617

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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