Which versions of sghrlhoxql are malicious?

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

How do I remediate sghrlhoxql if I installed it?

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

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

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

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

Malicious package

sghrlhoxqlRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8607

Immediate action

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

gem uninstall sghrlhoxql

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

898453b04f6cd783e7ae642655e390854eb3658ec680326cbf00d9d527ea141e

e232d0424653536ac7c8e461de9750bed9cf883cddf3c9e7965dc012e245b10c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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