Which versions of zlam_newcalok are malicious?

The following RubyGems versions of zlam_newcalok are flagged malicious: 0.0.201. Treat any of these as compromised.

How do I remediate zlam_newcalok if I installed it?

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

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

Yes — zlam_newcalok is associated with the RLMA-2026-04292, RLUA-2026-10229 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_newcalok across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for zlam_newcalok (version 0.0.201).

Malicious package

zlam_newcalokRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zlam_newcalok (RubyGems)

MAL-2026-9640

Immediate action

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

gem uninstall zlam_newcalok

Malicious versions

1 flagged

0.0.201

Indicators of compromise (SHA-256)

d86f2ba8de04ed48241cd9a21952ef5e390e19436361bbb34ca991870ed3205b

b3a655b9be0d04f64a0aad92b09b67a016967eaae070aad69200f2b7e9324df6

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04292RLUA-2026-10229

References

Credits

ReversingLabs · finder

Detect & block this

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