Which versions of zlam_hjana are malicious?

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

How do I remediate zlam_hjana if I installed it?

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

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

Yes — zlam_hjana is associated with the RLMA-2026-04275, RLUA-2026-10212 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_hjana across my projects, lockfiles, and CI pipelines?

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

Malicious package

zlam_hjanaRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zlam_hjana is a confirmed malicious RubyGems package (MAL-2026-9624) 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_hjana (RubyGems)

MAL-2026-9624

Immediate action

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

gem uninstall zlam_hjana

Malicious versions

1 flagged

0.0.204

Indicators of compromise (SHA-256)

1b565211e73a57d9c0be6ca3fc2bb6bfafbec6fa331ba90ceab63fa8bdfafd72

338fbc03d1eac422864cacef3836c9ce245fb0da6ce0520b54c2224c3e2e8fc1

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zlam_hjana (version 0.0.204).
If you installed it — respond
Remove zlam_hjana 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_hjana 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_hjana 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-04275RLUA-2026-10212

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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