Which versions of zlam_cal29 are malicious?

The following RubyGems versions of zlam_cal29 are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate zlam_cal29 if I installed it?

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

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

Yes — zlam_cal29 is associated with the RLMA-2026-04269, RLUA-2026-10206 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_cal29 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for zlam_cal29 (version 0.0.1).

Malicious package

zlam_cal29RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zlam_cal29 (RubyGems)

MAL-2026-9618

Immediate action

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

gem uninstall zlam_cal29

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

522e18bca692b37f7cb4853714d74a4acb1e329dca6f4d7ddd51bf6c21d918d9

3f0ac743ed5e7c2045d1942128e321079d61505829305f6a89e1e125120e4193

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04269RLUA-2026-10206

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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