Which versions of lat2cal1 are malicious?

The following RubyGems versions of lat2cal1 are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate lat2cal1 if I installed it?

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

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

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

Search your lockfiles and build artifacts for lat2cal1 (version 0.0.2).

Malicious package

lat2cal1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in lat2cal1 (RubyGems)

MAL-2026-7902

Immediate action

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

gem uninstall lat2cal1

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

640d43bab4abc1998c08bec353c1ec686a09597b90ce0a98d9f70273c5c11b2d

627af6da9650439272147d6b8132dc066bac1b086e03347814f850a34e546f16

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02553RLUA-2026-08370

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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