Which versions of rfetch3 are malicious?

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

How do I remediate rfetch3 if I installed it?

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

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

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

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

Malicious package

rfetch3RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8512

Immediate action

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

gem uninstall rfetch3

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3be6cde81f95cd11409494cfc47adb8f099986377d4857737953321ea61473f0

2c3c0a291650a2b52dcf3c2cc9e26994b2531d58ee39e4aa53a2c9922acb2fc3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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