Which versions of lcalx1368278 are malicious?

The following RubyGems versions of lcalx1368278 are flagged malicious: 0.0.68278. Treat any of these as compromised.

How do I remediate lcalx1368278 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lcalx1368278 (version 0.0.68278).

Malicious package

lcalx1368278RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lcalx1368278 (RubyGems)

MAL-2026-7979

Immediate action

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

gem uninstall lcalx1368278

Malicious versions

1 flagged

0.0.68278

Indicators of compromise (SHA-256)

fe1c96603f1a3c637e6e5fc9531f78ae755dd42caa93c4d76a099c669ebdbdc1

0fe54ef5be8e6b4dacee7a0795e757d469aebf1ffa30d7e453e3eddb6c5744df

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02630RLUA-2026-08447

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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