Which versions of zlam_cal28 are malicious?

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

How do I remediate zlam_cal28 if I installed it?

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

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

Yes — zlam_cal28 is associated with the RLMA-2026-04268, RLUA-2026-10205 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_cal28 across my projects, lockfiles, and CI pipelines?

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

Malicious package

zlam_cal28RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zlam_cal28 is a confirmed malicious RubyGems package (MAL-2026-9617) 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_cal28 (RubyGems)

MAL-2026-9617

Immediate action

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

gem uninstall zlam_cal28

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

119c0627b85c0db8f385023a1259d2a461d83067c0c31a5171cd1d371159a7e6

fae8ff814e0ea7f01869a08601251ee9555df8f8e700a6a032d6bbbbfd5290d3

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zlam_cal28 (version 0.0.1).
If you installed it — respond
Remove zlam_cal28 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_cal28 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_cal28 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-04268RLUA-2026-10205

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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