Which versions of rfetchf are malicious?

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

How do I remediate rfetchf if I installed it?

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

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

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

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

Malicious package

rfetchfRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8521

Immediate action

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

gem uninstall rfetchf

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3f78627000be259f5089ef7ca8c37b81a5119ddb30122010fc4e6b93e3badb6a

6a53504735ceace1b1fee5f5018a0dcb1eb2d031812805e756fcaf3a62da6d10

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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