Which versions of sgekvdhxno are malicious?

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

How do I remediate sgekvdhxno if I installed it?

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

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

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

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

Malicious package

sgekvdhxnoRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8599

Immediate action

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

gem uninstall sgekvdhxno

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

edf844fa1728ce8dfb764be16cfe04397b4d6d375a9830af64517a9ec51ddc48

aa3c2fbd5a9dbc7116ea457e13e5c370529ee0bb7616e8e49cba2dc595077369

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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