Which versions of saeb369b8c are malicious?

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

How do I remediate saeb369b8c if I installed it?

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

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

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

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

Malicious package

saeb369b8cRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8573

Immediate action

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

gem uninstall saeb369b8c

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ff2f39b1177e03b72b6693cc003d7a8a79687138db23936e5fb743dcbd1400cb

ebe69eee092535f33454c79660bdd02c827ec3e7599e5c36a0d2806d924db29f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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