Which versions of lcrzsrkysea are malicious?

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

How do I remediate lcrzsrkysea if I installed it?

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

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

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

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

Malicious package

lcrzsrkyseaRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7987

Immediate action

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

gem uninstall lcrzsrkysea

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d92dd1e9e5beca0ce22668ac56b3a553f89169fd597e6e282bcf749824e09c37

33f26b7b3f1ba2e1a6270ca41075b1353b1e433d136ff92d90da6d1f0f73a299

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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