Which versions of zhcal0b8005 are malicious?

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

How do I remediate zhcal0b8005 if I installed it?

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

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

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

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

Malicious package

zhcal0b8005RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9571

Immediate action

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

gem uninstall zhcal0b8005

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

dace33f3b02811f990e6f6a1b33609a3662c44ca593445a96ebd963a9c7064d8

a93fb06a8bc5e5a987c54dd8ddc51e4f12735b93fb3fdb160df4f3cb138a52b9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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