Which versions of lcalx0768249 are malicious?

The following RubyGems versions of lcalx0768249 are flagged malicious: 0.0.68249. Treat any of these as compromised.

How do I remediate lcalx0768249 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lcalx0768249 (version 0.0.68249).

Malicious package

lcalx0768249RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lcalx0768249 (RubyGems)

MAL-2026-7973

Immediate action

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

gem uninstall lcalx0768249

Malicious versions

1 flagged

0.0.68249

Indicators of compromise (SHA-256)

ee4efcd993e940808ec4c29afdca3b91a8966b7611b1412ce034f61fac5c92cf

cc429418e89aef3516ee384b6f5fc8ef8b5153d77938dee79f0e73c88de5e95d

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02624RLUA-2026-08441

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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