Which versions of sa9695b9d2 are malicious?

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

How do I remediate sa9695b9d2 if I installed it?

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

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

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

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

Malicious package

sa9695b9d2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8568

Immediate action

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

gem uninstall sa9695b9d2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

be45076153e13f2ce5d7f51262833766621598fc5cb737f3b9eb372d2d942ffe

634c76d5dbc2dfc3f1f20e9c92c01a627e07125afa3967314390465a56fddd31

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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