Which versions of lckxcksgmwc are malicious?

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

How do I remediate lckxcksgmwc if I installed it?

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

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

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

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

Malicious package

lckxcksgmwcRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7985

Immediate action

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

gem uninstall lckxcksgmwc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e9bf69ebefe80c10276c20c25958a20d1d2de17e3e67f29e58f07e906f874a70

3710986b36e6e5a51b2e276122129fc122a28cc439965080b53b5208ea75ce7a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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