Which versions of rfetchg are malicious?

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

How do I remediate rfetchg if I installed it?

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

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

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

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

Malicious package

rfetchgRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8522

Immediate action

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

gem uninstall rfetchg

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

45546d84af67c6825887a54b2237a94aece851c296e57a6bf55e6034e028607c

cfb05698f92e73d5f6300d3cafd653cd01c8a36a2712da9e7524eca8b29f8854

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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