Which versions of sghizaeigy are malicious?

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

How do I remediate sghizaeigy if I installed it?

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

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

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

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

Malicious package

sghizaeigyRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8606

Immediate action

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

gem uninstall sghizaeigy

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9a441090ecd99d0fd5e2e0514d259000f161bcfb39d6fbecd38a9fe73b53cd4d

b4bfd5d58674a81a6d9fbad1e92445da59c2796347eb639f154f1d8fe4c5b0e5

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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