Which versions of wfetch6a028604a are malicious?

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

How do I remediate wfetch6a028604a if I installed it?

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

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

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

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

Malicious package

wfetch6a028604aRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9328

Immediate action

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

gem uninstall wfetch6a028604a

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

105173448aca48e31d5133e7a03b1127b9e8af96335af53c56b4f5f29b89885f

fefb7192be935e66809441b75fc443ecd5c96b63fdead94cc38e9d3cc9840578

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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