Which versions of zhgx02ab9f are malicious?

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

How do I remediate zhgx02ab9f if I installed it?

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

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

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

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

Malicious package

zhgx02ab9fRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9577

Immediate action

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

gem uninstall zhgx02ab9f

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fb5aaf0d18e544a2be364a99e1fab553dc95adf01180201117364da02a2a6748

7fcb585956a9c13b46203acf0855283d271b74d409e3893932ff94a91e887282

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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