Which versions of lcalx0068214 are malicious?

The following RubyGems versions of lcalx0068214 are flagged malicious: 0.0.68214. Treat any of these as compromised.

How do I remediate lcalx0068214 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lcalx0068214 (version 0.0.68214).

Malicious package

lcalx0068214RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lcalx0068214 (RubyGems)

MAL-2026-7966

Immediate action

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

gem uninstall lcalx0068214

Malicious versions

1 flagged

0.0.68214

Indicators of compromise (SHA-256)

e8657d21b66f8734f6f7c4f6e837f6d6864e6ce44b7e916fdec964fd0a1947a1

f37e6cc3ec714f4cb91fc67315b05b8ed0b8ae1935c2b49763672c974d93bd43

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02617RLUA-2026-08434

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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