Which versions of xcafdc17579 are malicious?

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

How do I remediate xcafdc17579 if I installed it?

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

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

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

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

Malicious package

xcafdc17579RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9521

Immediate action

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

gem uninstall xcafdc17579

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c398d9fb48c6328dd84d6516dc8229723ccac6e08a574e89cd4b2c84bdb7c5a7

6f4e0bd2e663a2fda887764bb35f72d2ab1ad9478fa9738716eba15020dc30bb

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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