Which versions of lcalx1668291 are malicious?

The following RubyGems versions of lcalx1668291 are flagged malicious: 0.0.68291. Treat any of these as compromised.

How do I remediate lcalx1668291 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lcalx1668291 (version 0.0.68291).

Malicious package

lcalx1668291RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

lcalx1668291 is a confirmed malicious RubyGems package (MAL-2026-7982) that executes malicious code on install (malicious version 0.0.68291). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lcalx1668291 (RubyGems)

MAL-2026-7982

Immediate action

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

gem uninstall lcalx1668291

Malicious versions

1 flagged

0.0.68291

Indicators of compromise (SHA-256)

09ef0d4aba3bbb6a7acddde88132808ceec3809176d7f556163161c1dae70bce

d9c89a5ab997add67a1ca91b2b4fa97f9b62ffcc46acbe6fa3f626825a092cd5

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for lcalx1668291 (version 0.0.68291).
If you installed it — respond
Remove lcalx1668291 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 lcalx1668291 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. lcalx1668291 on RubyGems has been identified as a malicious package (version 0.0.68291 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-02633RLUA-2026-08450

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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