Which versions of sa20a7aec4 are malicious?

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

How do I remediate sa20a7aec4 if I installed it?

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

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

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

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

Malicious package

sa20a7aec4RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8560

Immediate action

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

gem uninstall sa20a7aec4

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3142f960b8838beb189a938ae51e7fdc561c9d8fec9b790c246379ad0f90da22

538daf1e3e4aedf380a0e5080641594082ce95763b13c1df35df367643ab8dd2

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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