Which versions of saee8cba76 are malicious?

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

How do I remediate saee8cba76 if I installed it?

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

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

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

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

Malicious package

saee8cba76RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8574

Immediate action

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

gem uninstall saee8cba76

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8efd5c4e36724e390a27a55b03b59a3eca6c5a8eaba3c77cdc54c36419cb3d0c

e5f3f0a9f656ca7dd4676af1421788c89f6b94475183a08102e7c8e0aa001e97

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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