Which versions of zrhgcapa are malicious?

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

How do I remediate zrhgcapa if I installed it?

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

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

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

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

Malicious package

zrhgcapaRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9754

Immediate action

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

gem uninstall zrhgcapa

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e0f43aa5c82416bff8e801b7f471db2038629dbcd81c62a49155f6818693239f

ae7f11e1c7e2cd46203267aa4dd9e1ceee13e5f51a3c8ad6db56c10d671aa0b9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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