Which versions of zlam_newcalYY are malicious?

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

How do I remediate zlam_newcalYY if I installed it?

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

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

Yes — zlam_newcalYY is associated with the RLMA-2026-04291, RLUA-2026-10228 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_newcalYY across my projects, lockfiles, and CI pipelines?

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

Malicious package

zlam_newcalYYRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zlam_newcalYY is a confirmed malicious RubyGems package (MAL-2026-9641) 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_newcalYY (RubyGems)

MAL-2026-9641

Immediate action

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

gem uninstall zlam_newcalYY

Malicious versions

1 flagged

0.0.201

Indicators of compromise (SHA-256)

a5e6233d6fdf1cbb9c119ed3ade0ae2e663b2d387cf0291f3138012f9b721ad7

6f29a9a686a91633d5913cba19f78ebeef5de30c81a1619adfc725231ef4ea57

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zlam_newcalYY (version 0.0.201).
If you installed it — respond
Remove zlam_newcalYY 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_newcalYY 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_newcalYY 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-04291RLUA-2026-10228

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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