Which versions of zlam_hjanf are malicious?

The following RubyGems versions of zlam_hjanf are flagged malicious: 0.0.204. Treat any of these as compromised.

How do I remediate zlam_hjanf if I installed it?

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

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

Yes — zlam_hjanf is associated with the RLMA-2026-04280, RLUA-2026-10217 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_hjanf across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for zlam_hjanf (version 0.0.204).

Malicious package

zlam_hjanfRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zlam_hjanf (RubyGems)

MAL-2026-9629

Immediate action

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

gem uninstall zlam_hjanf

Malicious versions

1 flagged

0.0.204

Indicators of compromise (SHA-256)

a0567523c7ff7f17316f36d99d8e02cbd5c35fa6a3edd9522917fe064e318140

4299b714e269c836e46b8510e545c84f6ad075ad93605015beca1581adf44bb3

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04280RLUA-2026-10217

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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