Which versions of lcalx0568239 are malicious?

The following RubyGems versions of lcalx0568239 are flagged malicious: 0.0.68239. Treat any of these as compromised.

How do I remediate lcalx0568239 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lcalx0568239 (version 0.0.68239).

Malicious package

lcalx0568239RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lcalx0568239 (RubyGems)

MAL-2026-7971

Immediate action

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

gem uninstall lcalx0568239

Malicious versions

1 flagged

0.0.68239

Indicators of compromise (SHA-256)

bd3648cde9db7667b395a32b479305617ccad841b2a1c5ea79a9073ada1e0420

3ea63b2e28fca4bdcfc182b0dba1221c61824f71fc69ef9fcbe8ae4f4be64955

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02622RLUA-2026-08439

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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