Which versions of sgicgptpuh are malicious?

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

How do I remediate sgicgptpuh if I installed it?

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

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

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

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

Malicious package

sgicgptpuhRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8610

Immediate action

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

gem uninstall sgicgptpuh

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9252ee0510eee1dc62d1af2a194bd685480792fdb59f839f37b5f66cd506fd21

939d6e24b3c26088a86661a95f2fe37b8771fed34d9a0aa1115a4f46e4d62735

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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