Which versions of sgxqzbqqph are malicious?

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

How do I remediate sgxqzbqqph if I installed it?

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

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

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

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

Malicious package

sgxqzbqqphRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8627

Immediate action

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

gem uninstall sgxqzbqqph

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b7ceb8c0ab28941ad3073d1d5abc615a19c39090da86aa5ba1c3c9deab23e177

4d98cb3333b5bee3820fd39b028967e638667adf7a4c8dbf41ad2a46f09e3a60

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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