Which versions of lcalx0668245 are malicious?

The following RubyGems versions of lcalx0668245 are flagged malicious: 0.0.68245. Treat any of these as compromised.

How do I remediate lcalx0668245 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lcalx0668245 (version 0.0.68245).

Malicious package

lcalx0668245RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lcalx0668245 (RubyGems)

MAL-2026-7972

Immediate action

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

gem uninstall lcalx0668245

Malicious versions

1 flagged

0.0.68245

Indicators of compromise (SHA-256)

d8e79f926ce8e6e56a849052726dee03b4b7be56de7dbe4ba98c1158205af0a0

35226a5a783383d7c25983030e70abcd288639aa22501bebd97c734d2680337a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02623RLUA-2026-08440

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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