Which versions of sx638fce are malicious?

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

How do I remediate sx638fce if I installed it?

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

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

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

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

Malicious package

sx638fceRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8964

Immediate action

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

gem uninstall sx638fce

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5857567268a2eecf4c2e36e7cd42cb33717bd344eec85258b6a35801a4c980d2

1a9a4ce92affca93ba01e492adff620b973e53c7f22a82889ce7ae34a110a3b0

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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