Which versions of lcalx1468283 are malicious?

The following RubyGems versions of lcalx1468283 are flagged malicious: 0.0.68283. Treat any of these as compromised.

How do I remediate lcalx1468283 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lcalx1468283 (version 0.0.68283).

Malicious package

lcalx1468283RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lcalx1468283 (RubyGems)

MAL-2026-7980

Immediate action

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

gem uninstall lcalx1468283

Malicious versions

1 flagged

0.0.68283

Indicators of compromise (SHA-256)

99995b393c4c869a8630eb24e51b4d6d74ebc57d7f1f90ffa816e911b221299f

c8701a14799636cc03e4019f44b4a0dd3893ada10a4899dd8f7e682dcb9b938c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02631RLUA-2026-08448

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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