Which versions of sghsvfnjgk are malicious?

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

How do I remediate sghsvfnjgk if I installed it?

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

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

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

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

Malicious package

sghsvfnjgkRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8608

Immediate action

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

gem uninstall sghsvfnjgk

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2d46e4b9a7ae2b0c492b118cce758ab435979ce75ee852746aa4b714ac5fb749

04e0fb0f337fa5cd531349d5fb032c29517e8bcccbc640bbf9504fdb3f2cfc40

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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