Which versions of hackysouthfetch are malicious?

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

How do I remediate hackysouthfetch if I installed it?

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

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

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

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

Malicious package

hackysouthfetchRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-7733

Immediate action

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

gem uninstall hackysouthfetch

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e592fd73cf51ee196e395517a51f851f702d81dbdfe2ef18c082ca29fe5821f6

86ba0e22a3d54536fb1e4b8eaf30373ad89a7e27f6cae996d8aede5c421d21d3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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