Which versions of sa6ed9cec3 are malicious?

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

How do I remediate sa6ed9cec3 if I installed it?

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

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

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

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

Malicious package

sa6ed9cec3RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8564

Immediate action

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

gem uninstall sa6ed9cec3

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a0099c7e160929d852e5c9a7da679e453a8a5327b21a588c8a5b052717055adf

b3f7de52a945671f8dcff283b5b97324d63b0f07009ed7ff2c942e0403c37f6e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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