Which versions of sgccmmheke are malicious?

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

How do I remediate sgccmmheke if I installed it?

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

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

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

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

Malicious package

sgccmmhekeRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8598

Immediate action

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

gem uninstall sgccmmheke

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3dee64ae7627663f2eb16d6cded40ddeb1014739328c3b6bbd1e2e8fbffdbbf2

009917b99000d47ace30dfe753e2a885b891c862e6b45c2741343f64fc7e609f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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