Which versions of lcalx1268273 are malicious?

The following RubyGems versions of lcalx1268273 are flagged malicious: 0.0.68273. Treat any of these as compromised.

How do I remediate lcalx1268273 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lcalx1268273 (version 0.0.68273).

Malicious package

lcalx1268273RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lcalx1268273 (RubyGems)

MAL-2026-7978

Immediate action

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

gem uninstall lcalx1268273

Malicious versions

1 flagged

0.0.68273

Indicators of compromise (SHA-256)

08af66f0acc7603f26a5e8421232b9180865c49b9cca95c94beb22d2e7ed09ae

219ac41c43b2d421840c9281474e3c2245f1d52ed8bbe4f5bc2234bf83127b6f

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02629RLUA-2026-08446

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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