Which versions of sgxnwefney are malicious?

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

How do I remediate sgxnwefney if I installed it?

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

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

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

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

Malicious package

sgxnwefneyRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8626

Immediate action

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

gem uninstall sgxnwefney

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

99bc6dbe1d42980e8f7610ca2621d1711d64e98e2da1a844a7f221148c731d41

c4235405c86aa4b9b1315c288a369a0e939ed0489177a6d3e6bec4cf617cf5c1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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