Which versions of zlam_httpm are malicious?

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

How do I remediate zlam_httpm if I installed it?

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

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

Yes — zlam_httpm is associated with the RLMA-2026-04284, RLUA-2026-10221 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_httpm across my projects, lockfiles, and CI pipelines?

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

Malicious package

zlam_httpmRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zlam_httpm is a confirmed malicious RubyGems package (MAL-2026-9633) 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_httpm (RubyGems)

MAL-2026-9633

Immediate action

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

gem uninstall zlam_httpm

Malicious versions

1 flagged

0.0.202

Indicators of compromise (SHA-256)

467f9d2952f2c947847027691572ed06edc4c1f0ad3edb486aff7f24f6f3b86c

5aa1a19be126faeaf5b2a9aeb49f49a3cc4bc486ad43f2c7510e9bfb07e8e3d6

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zlam_httpm (version 0.0.202).
If you installed it — respond
Remove zlam_httpm 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_httpm 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_httpm 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-04284RLUA-2026-10221

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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