Which versions of sghwnriwgq are malicious?

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

How do I remediate sghwnriwgq if I installed it?

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

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

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

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

Malicious package

sghwnriwgqRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8609

Immediate action

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

gem uninstall sghwnriwgq

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

870e431d673910bf83dabc3375145d86cbc194ad1059f5dc66559c742fcf29df

06b8ea3b472572a1b80ed614689a9fd5ca1ba8baad14db07ff4bfc8631576aff

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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