Which versions of lcalx0268224 are malicious?

The following RubyGems versions of lcalx0268224 are flagged malicious: 0.0.68224. Treat any of these as compromised.

How do I remediate lcalx0268224 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lcalx0268224 (version 0.0.68224).

Malicious package

lcalx0268224RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lcalx0268224 (RubyGems)

MAL-2026-7968

Immediate action

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

gem uninstall lcalx0268224

Malicious versions

1 flagged

0.0.68224

Indicators of compromise (SHA-256)

2f1ac3e024ca86a84f04e11757c496be3bc985e24881d5e311cb77680d8c593e

656ba94b83bdc1de2e8c57e37ac2ba3e4360d7131dccdc7a71f65e6caf471530

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02619RLUA-2026-08436

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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