Which versions of lcalx1568287 are malicious?

The following RubyGems versions of lcalx1568287 are flagged malicious: 0.0.68287. Treat any of these as compromised.

How do I remediate lcalx1568287 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lcalx1568287 (version 0.0.68287).

Malicious package

lcalx1568287RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lcalx1568287 (RubyGems)

MAL-2026-7981

Immediate action

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

gem uninstall lcalx1568287

Malicious versions

1 flagged

0.0.68287

Indicators of compromise (SHA-256)

a1b1822a0db5953beafc07aa2c4b72e231ada67f72ed59ae5b8d83f41f67a113

495308d8378203bc043a996172e12eda1ff2dbf857aecdef4677d8331936acdf

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02632RLUA-2026-08449

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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