Which versions of zlam_httpsm are malicious?

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

How do I remediate zlam_httpsm if I installed it?

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

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

Yes — zlam_httpsm is associated with the RLMA-2026-04286, RLUA-2026-10223 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_httpsm across my projects, lockfiles, and CI pipelines?

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

Malicious package

zlam_httpsmRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zlam_httpsm is a confirmed malicious RubyGems package (MAL-2026-9635) 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_httpsm (RubyGems)

MAL-2026-9635

Immediate action

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

gem uninstall zlam_httpsm

Malicious versions

1 flagged

0.0.202

Indicators of compromise (SHA-256)

2a1ccbe8c1cfcaeb472cd4ee02dbe94bdb3bf5ac3581f0da19622507684fdeab

9300825cb4cc5db0d91a40ecd293320aada069484a481123edc20ce9e6a053bb

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zlam_httpsm (version 0.0.202).
If you installed it — respond
Remove zlam_httpsm 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_httpsm 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_httpsm 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-04286RLUA-2026-10223

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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