Which versions of rfetchc are malicious?

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

How do I remediate rfetchc if I installed it?

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

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

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

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

Malicious package

rfetchcRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8518

Immediate action

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

gem uninstall rfetchc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4eda02d2b6ad85abe5f755aef9cd900df619795580d1c697a2faebac767f5423

f2a7b120113722db818e665e412fce7898af9fe13c8651bc6fe359a4fcb4c53c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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