Which versions of zlam_cal_jan1 are malicious?

The following RubyGems versions of zlam_cal_jan1 are flagged malicious: 0.0.135. Treat any of these as compromised.

How do I remediate zlam_cal_jan1 if I installed it?

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

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

Yes — zlam_cal_jan1 is associated with the RLMA-2026-04271, RLUA-2026-10208 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_jan1 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for zlam_cal_jan1 (version 0.0.135).

Malicious package

zlam_cal_jan1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zlam_cal_jan1 (RubyGems)

MAL-2026-9620

Immediate action

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

gem uninstall zlam_cal_jan1

Malicious versions

1 flagged

0.0.135

Indicators of compromise (SHA-256)

4fca2010e4832753d433e74c14dcae58b5911b73124ab13186ed4154513e0347

2119a4987e40f978fce3f95c13c8bff5589b03b26be9305f71463497176109f4

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04271RLUA-2026-10208

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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