Which versions of lcalx0168219 are malicious?

The following RubyGems versions of lcalx0168219 are flagged malicious: 0.0.68219. Treat any of these as compromised.

How do I remediate lcalx0168219 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lcalx0168219 (version 0.0.68219).

Malicious package

lcalx0168219RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lcalx0168219 (RubyGems)

MAL-2026-7967

Immediate action

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

gem uninstall lcalx0168219

Malicious versions

1 flagged

0.0.68219

Indicators of compromise (SHA-256)

74f9de43c80d9f4e2d90d359996aedec10c91cb9beeab6d2e5fc86a9caea6761

0227c1c035556b4a6c0c797b23abfefbc84df53d1b031b33fed570eb25d841fc

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02618RLUA-2026-08435

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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