Which versions of sgpajdnsoz are malicious?

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

How do I remediate sgpajdnsoz if I installed it?

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

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

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

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

Malicious package

sgpajdnsozRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8615

Immediate action

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

gem uninstall sgpajdnsoz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a56a7a86fba873e7cbf68d5dfc226cb4e78dcdff5570a3ef9ee3a7df850240ce

894a67a9b937c09c7de94807b8803be56d2d78d053a4fa2b3b51270450f56716

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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