Which versions of rfetchh are malicious?

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

How do I remediate rfetchh if I installed it?

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

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

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

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

Malicious package

rfetchhRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8523

Immediate action

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

gem uninstall rfetchh

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

081ae0942a9cf54616c696ab8703edbe56169dc4218200fa36a2b7f6aa9f67dc

00c6a33fde627e6c1a8a3aa5fc487d49aadee48733638b999b9fa684497d4217

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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