Which versions of zlam_cal_jan2 are malicious?

The following RubyGems versions of zlam_cal_jan2 are flagged malicious: 0.0.136. Treat any of these as compromised.

How do I remediate zlam_cal_jan2 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zlam_cal_jan2 (version 0.0.136).

Malicious package

zlam_cal_jan2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zlam_cal_jan2 (RubyGems)

MAL-2026-9621

Immediate action

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

gem uninstall zlam_cal_jan2

Malicious versions

1 flagged

0.0.136

Indicators of compromise (SHA-256)

05cda573093ddc98e5c39f0948e7d1694680219800f283c12757025df72f9cd9

cce411a29ca8cc08c807dc12b15d7463c598270b73db056a0dd94b799e7a33ea

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04272RLUA-2026-10209

References

Credits

ReversingLabs · finder

Detect & block this

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