Which versions of sgrernmauc are malicious?

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

How do I remediate sgrernmauc if I installed it?

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

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

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

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

Malicious package

sgrernmaucRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8619

Immediate action

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

gem uninstall sgrernmauc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9fa17ac7b7df1ca372495542ed7f901e88de9dd9c09a0e94b23be945126a248b

dfc470ee065bad90edeb730ee2fdb4cb9fd5c35aa6d348eed2eb1df96030e23b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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