Which versions of sgxdhvmbhl are malicious?

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

How do I remediate sgxdhvmbhl if I installed it?

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

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

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

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

Malicious package

sgxdhvmbhlRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8625

Immediate action

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

gem uninstall sgxdhvmbhl

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

361985f6d3cc85cdaf3796f650644de7e796d4102470d2e453a2c029466aa48f

7bca295187243e21df25061cf009c8f03ab95d1d9afbe6a920e95002e071d074

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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