Which versions of zhcalf4ed55 are malicious?

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

How do I remediate zhcalf4ed55 if I installed it?

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

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

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

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

Malicious package

zhcalf4ed55RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zhcalf4ed55 is a confirmed malicious RubyGems package (MAL-2026-9575) 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 zhcalf4ed55 (RubyGems)

MAL-2026-9575

Immediate action

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

gem uninstall zhcalf4ed55

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b7877cdca28cf487e6b87658d75c1b91aead4e92069c6e2fdd60fffbfff2b3c7

d6fc80d4bb6c5ae3dc759ddfbf323e13ee99dbcd875f44f2856da221f8c40ee7

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zhcalf4ed55 (version 0.0.1).
If you installed it — respond
Remove zhcalf4ed55 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 zhcalf4ed55 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. zhcalf4ed55 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-04226RLUA-2026-10163

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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