Which versions of sa64ce1145 are malicious?

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

How do I remediate sa64ce1145 if I installed it?

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

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

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

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

Malicious package

sa64ce1145RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8563

Immediate action

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

gem uninstall sa64ce1145

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

72c8df1032d64ac3e5908623dec14c8f8429c772334c4719a3dc2819d917430b

6c83755ac424b1ed3804a548d478f57b59fb400ea02cd67880ed0609610f2f4e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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