Which versions of sacb0f5cd9 are malicious?

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

How do I remediate sacb0f5cd9 if I installed it?

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

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

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

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

Malicious package

sacb0f5cd9RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8570

Immediate action

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

gem uninstall sacb0f5cd9

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

186d2e6995b5f140c0b059e4e5b68712313015b9c23035720193a3b1d09201f0

4cc20baedd899a95268968c4822de082cda054dc362034bbb0bdd779a1bb1b82

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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