Which versions of lcalx0868254 are malicious?

The following RubyGems versions of lcalx0868254 are flagged malicious: 0.0.68254. Treat any of these as compromised.

How do I remediate lcalx0868254 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lcalx0868254 (version 0.0.68254).

Malicious package

lcalx0868254RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lcalx0868254 (RubyGems)

MAL-2026-7974

Immediate action

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

gem uninstall lcalx0868254

Malicious versions

1 flagged

0.0.68254

Indicators of compromise (SHA-256)

f343acd532320f5fd20e5aaffb13fa25407b5f134dc35c299ddb1a73f4be2b0a

78fdbad4e6df898d4eb6bbef0dddc1e35e078ddf6c3f9cf9fe16200607c5926d

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02625RLUA-2026-08442

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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