Which versions of lcalx1168268 are malicious?

The following RubyGems versions of lcalx1168268 are flagged malicious: 0.0.68268. Treat any of these as compromised.

How do I remediate lcalx1168268 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lcalx1168268 (version 0.0.68268).

Malicious package

lcalx1168268RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lcalx1168268 (RubyGems)

MAL-2026-7977

Immediate action

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

gem uninstall lcalx1168268

Malicious versions

1 flagged

0.0.68268

Indicators of compromise (SHA-256)

8d499f8cf62df76c64543d9af07c8700bb0697e6ac69fbd71c6eaf412edec523

5e8babaa0ac61437160a5f4a46c5736df7ff410897f2fcda50f78b448de6a79c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02628RLUA-2026-08445

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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