Which versions of zlam_root are malicious?

The following RubyGems versions of zlam_root are flagged malicious: 0.0.202. Treat any of these as compromised.

How do I remediate zlam_root if I installed it?

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

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

Yes — zlam_root is associated with the RLMA-2026-04293, RLUA-2026-10230 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_root across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for zlam_root (version 0.0.202).

Malicious package

zlam_rootRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zlam_root (RubyGems)

MAL-2026-9642

Immediate action

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

gem uninstall zlam_root

Malicious versions

1 flagged

0.0.202

Indicators of compromise (SHA-256)

f33de9eab623c35edde97e0d3a064b881fef45d3475933965b4c9459cb119d0f

211030714e937447b065b171ceb194634594b16be7f6bd892b6468cfac01ee2c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04293RLUA-2026-10230

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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