Which versions of sgfesdiqyo are malicious?

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

How do I remediate sgfesdiqyo if I installed it?

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

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

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

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

Malicious package

sgfesdiqyoRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8602

Immediate action

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

gem uninstall sgfesdiqyo

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

87d0b57255c1d0aa87070f53ec4c8b6221efe9f26e74b74309ab61a5ef3f6a58

b88ae2a59006e2df064c2a70e507515eb5bbec81dede75dde5cafe0f8f6bb7ab

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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