Which versions of zlam_hjanb are malicious?

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

How do I remediate zlam_hjanb if I installed it?

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

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

Yes — zlam_hjanb is associated with the RLMA-2026-04276, RLUA-2026-10213 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_hjanb across my projects, lockfiles, and CI pipelines?

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

Malicious package

zlam_hjanbRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zlam_hjanb is a confirmed malicious RubyGems package (MAL-2026-9625) 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_hjanb (RubyGems)

MAL-2026-9625

Immediate action

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

gem uninstall zlam_hjanb

Malicious versions

1 flagged

0.0.204

Indicators of compromise (SHA-256)

992bf2e93f18fd08ca5af53b78d954c473b1e5646772b98e611cbaaaafeeff37

d82c3f8dd349671a2ea8fbafffceb56701dba3336920266ae41c461326e7df70

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zlam_hjanb (version 0.0.204).
If you installed it — respond
Remove zlam_hjanb 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_hjanb 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_hjanb 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-04276RLUA-2026-10213

References

Credits

ReversingLabs · finder

Detect & block this

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