Which versions of zlam_httpno are malicious?

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

How do I remediate zlam_httpno if I installed it?

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

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

Yes — zlam_httpno is associated with the RLMA-2026-04285, RLUA-2026-10222 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_httpno across my projects, lockfiles, and CI pipelines?

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

Malicious package

zlam_httpnoRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zlam_httpno is a confirmed malicious RubyGems package (MAL-2026-9634) 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_httpno (RubyGems)

MAL-2026-9634

Immediate action

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

gem uninstall zlam_httpno

Malicious versions

1 flagged

0.0.202

Indicators of compromise (SHA-256)

21c3c66a4146f700c43dc0285b89eaa398bcb304e953901154ff30b3bc29ff69

11343313b09b00940f1ccdd8df88cdfaa4f7a43461745f889d947e3c20d7fe9d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zlam_httpno (version 0.0.202).
If you installed it — respond
Remove zlam_httpno 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_httpno 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_httpno 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-04285RLUA-2026-10222

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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