Which versions of gexpfetchxyz are malicious?

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

How do I remediate gexpfetchxyz if I installed it?

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

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

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

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

Malicious package

gexpfetchxyzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7713

Immediate action

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

gem uninstall gexpfetchxyz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7ee5fc35dafa725b6525ef4b6122c81dd8a29f2a5c71dd12a066c05118e6610f

80518d420e8a795777eeafb7a640c50f613505083720397902def1568d91d2ed

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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