Which versions of zlam_hjanh are malicious?

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

How do I remediate zlam_hjanh if I installed it?

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

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

Yes — zlam_hjanh is associated with the RLMA-2026-04282, RLUA-2026-10219 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_hjanh across my projects, lockfiles, and CI pipelines?

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

Malicious package

zlam_hjanhRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zlam_hjanh is a confirmed malicious RubyGems package (MAL-2026-9631) 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_hjanh (RubyGems)

MAL-2026-9631

Immediate action

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

gem uninstall zlam_hjanh

Malicious versions

1 flagged

0.0.204

Indicators of compromise (SHA-256)

40602cea7fedca0050520f89723d2ece6986837c35f5c786ed3cfa2cde0d76cc

d4b29b54eee27c2abe6b4d1b7f34bed8a8f3ae0bccda5057cd209b1b428724a1

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zlam_hjanh (version 0.0.204).
If you installed it — respond
Remove zlam_hjanh 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_hjanh 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_hjanh 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-04282RLUA-2026-10219

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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