Which versions of lcalx0968259 are malicious?

The following RubyGems versions of lcalx0968259 are flagged malicious: 0.0.68259. Treat any of these as compromised.

How do I remediate lcalx0968259 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lcalx0968259 (version 0.0.68259).

Malicious package

lcalx0968259RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lcalx0968259 (RubyGems)

MAL-2026-7975

Immediate action

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

gem uninstall lcalx0968259

Malicious versions

1 flagged

0.0.68259

Indicators of compromise (SHA-256)

e90e77af4fc6f7fce51d164e8690fa50163f184c726b22e52b6a2c5d9f405550

bcc34b46208abe1854908d677032d9f954f3bfd676fd071c6da63509a3ed940e

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02626RLUA-2026-08443

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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