Which versions of sgxbvusaqz are malicious?

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

How do I remediate sgxbvusaqz if I installed it?

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

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

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

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

Malicious package

sgxbvusaqzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8624

Immediate action

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

gem uninstall sgxbvusaqz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

abd68292b91a6a266ebc0ce96c935a4aebbcef1d1ba9f2b31feb246c6b20f9f6

ed3e6c6aae6826a1f77d0bd032d72ded65f1a72e4d599a01b9e86d1ddd873834

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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