Which versions of rfetch6 are malicious?

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

How do I remediate rfetch6 if I installed it?

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

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

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

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

Malicious package

rfetch6RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8515

Immediate action

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

gem uninstall rfetch6

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

62abf658df69ab322ae7ea99f0005680ad7a7fd75e31c79755a04de9fed7527b

8b0dfba219d9c35a753fbb8b5813ebc78a086bf7e0afd7d4a4734e12714a3918

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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