Which versions of sac7635b0f are malicious?

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

How do I remediate sac7635b0f if I installed it?

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

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

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

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

Malicious package

sac7635b0fRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8569

Immediate action

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

gem uninstall sac7635b0f

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8a85d5354f75c81402257860c7e430a9a49fb587629b76c1a787a8996777a241

29b096ed44d7895496777c3bed1c4bb7418c4f10085a2bf23403c519873876da

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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