Which versions of sae6a0e752 are malicious?

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

How do I remediate sae6a0e752 if I installed it?

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

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

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

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

Malicious package

sae6a0e752RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8572

Immediate action

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

gem uninstall sae6a0e752

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

06507b3686873afd13386f3b9c9b58ad84a10a2f17cbcc4aea4d6e854b0ad9ab

27a56dc6aa37b233901109fad9e4f0837f0dbd67e31c7ff5f08bc47b997200ea

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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