Which versions of sa35a63c8a are malicious?

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

How do I remediate sa35a63c8a if I installed it?

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

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

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

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

Malicious package

sa35a63c8aRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8561

Immediate action

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

gem uninstall sa35a63c8a

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c0b7a8a9027defa84151d41678546aa42b3eec1e9d9c4a711aa268698e4a268f

4b31d360a784e44fa8670a53d13a7c99b7df3cb7764e0a5a85c017abe4d34804

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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