Which versions of speed-spider are malicious?

The following RubyGems versions of speed-spider are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate speed-spider if I installed it?

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

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

Yes — speed-spider is associated with the RLMA-2024-05829, RLUA-2024-10350, RLUA-2026-09406 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 speed-spider across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for speed-spider (version 0.0.2).

Malicious package

speed-spiderRubyGems

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

Malicious code in speed-spider (RubyGems)

MAL-2024-7024

Immediate action

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

gem uninstall speed-spider

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

1ebf072e56dc38d6c2bf41de52878576245ad23ec63cdcc3f8d3576ad8431548

d90dbfffa497a4aab342d45430029d2e6c290683115d6e478a7e4327891c30ac

36d6a29dbbffa5db1a5e3170847a0bca5eb581e7166073600d7ebd24d1f24a12

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05829RLUA-2024-10350RLUA-2026-09406

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks speed-spider-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