Which versions of rfetchb are malicious?

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

How do I remediate rfetchb if I installed it?

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

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

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

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

Malicious package

rfetchbRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8517

Immediate action

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

gem uninstall rfetchb

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e37bc9be68b64ec15b3a9474f23e922aa327b1ebec86057b84d6834a6afe75aa

2246b7a0a20ac395645f5c3831183528a1d44cba4716ba65ed6870e5129a7ef8

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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