Which versions of spider_gazelle are malicious?

The following RubyGems versions of spider_gazelle are flagged malicious: 3.2.0. Treat any of these as compromised.

How do I remediate spider_gazelle if I installed it?

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

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

Yes — spider_gazelle is associated with the RLMA-2024-05833, RLUA-2024-10354, RLUA-2026-09410 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 spider_gazelle across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for spider_gazelle (version 3.2.0).

Malicious package

spider_gazelleRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

spider_gazelle is a confirmed malicious RubyGems package (MAL-2024-7028) that executes malicious code on install (malicious version 3.2.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in spider_gazelle (RubyGems)

MAL-2024-7028

Immediate action

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

gem uninstall spider_gazelle

Malicious versions

1 flagged

3.2.0

Indicators of compromise (SHA-256)

890a76e743519bb28653d15de7bcb58f46ed2472c74078e0f848331162e6e869

d4b163d528c91bbb9a803adecd0d4a4b0384bf53184a36313022cb0212d59799

133835aa70898badd0021e81031726eb85d567767f44b3f4d8807b3012245645

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for spider_gazelle (version 3.2.0).
If you installed it — respond
Remove spider_gazelle 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 spider_gazelle 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. spider_gazelle on RubyGems has been identified as a malicious package (version 3.2.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-05833RLUA-2024-10354RLUA-2026-09410

References

Credits

ReversingLabs · finder

Detect & block this

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