Which versions of lcalx1068264 are malicious?

The following RubyGems versions of lcalx1068264 are flagged malicious: 0.0.68264. Treat any of these as compromised.

How do I remediate lcalx1068264 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lcalx1068264 (version 0.0.68264).

Malicious package

lcalx1068264RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lcalx1068264 (RubyGems)

MAL-2026-7976

Immediate action

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

gem uninstall lcalx1068264

Malicious versions

1 flagged

0.0.68264

Indicators of compromise (SHA-256)

7b00229506c190508f5a12193689d1ae7a81e7ea1e115da97d1274d00ac9e1eb

68bd02a7ee84b65fe9ceaf126303352739d7b52525d1a367f849801c1d459dd9

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02627RLUA-2026-08444

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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