Which versions of zlam_hjanc are malicious?

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

How do I remediate zlam_hjanc if I installed it?

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

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

Yes — zlam_hjanc is associated with the RLMA-2026-04277, RLUA-2026-10214 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_hjanc across my projects, lockfiles, and CI pipelines?

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

Malicious package

zlam_hjancRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zlam_hjanc is a confirmed malicious RubyGems package (MAL-2026-9626) 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_hjanc (RubyGems)

MAL-2026-9626

Immediate action

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

gem uninstall zlam_hjanc

Malicious versions

1 flagged

0.0.204

Indicators of compromise (SHA-256)

e9d50ee0efdbbe62d856777306f539b99916c82aebcd75ec3a346ed21e7321f1

8bffd0c655889b53d659b26e57062ffac5562f343588adf303119e7458e09cb1

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zlam_hjanc (version 0.0.204).
If you installed it — respond
Remove zlam_hjanc 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_hjanc 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_hjanc 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-04277RLUA-2026-10214

References

Credits

ReversingLabs · finder

Detect & block this

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