Which versions of rfetch5 are malicious?

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

How do I remediate rfetch5 if I installed it?

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

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

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

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

Malicious package

rfetch5RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8514

Immediate action

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

gem uninstall rfetch5

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1766c6069f53ce558b25718d52c93271c3d7fcaa98252a7016f2aa35f51b117a

19c08fa0abe802294beaf5e960c50aee73ab7da4e7c562c7b78cdf439c2ac14e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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