Which versions of zhcald5e4c6 are malicious?

The following RubyGems versions of zhcald5e4c6 are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate zhcald5e4c6 if I installed it?

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

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

Yes — zhcald5e4c6 is associated with the RLMA-2026-04225, RLUA-2026-10162 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 zhcald5e4c6 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for zhcald5e4c6 (version 0.0.1).

Malicious package

zhcald5e4c6RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zhcald5e4c6 (RubyGems)

MAL-2026-9574

Immediate action

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

gem uninstall zhcald5e4c6

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

229b66e500d32055acd149a5cace8aca076037c3c85316bd97763abb45553c10

3b981e6dfd3f8848135fdb976b66ac0d2a20f08b6e4eda4e0106609b53c152d2

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04225RLUA-2026-10162

References

Credits

ReversingLabs · finder

Detect & block this

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