Which versions of sgjqdnyybe are malicious?

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

How do I remediate sgjqdnyybe if I installed it?

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

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

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

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

Malicious package

sgjqdnyybeRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8612

Immediate action

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

gem uninstall sgjqdnyybe

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7bb287aee0a803c43b23473c0a289df180ee2336eb166f353409397c58f8a10e

34b811e4790fc8eae8d8d626a1e60d4ed7eb6540d7bbc1b78a30b6dd4089539c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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