Which versions of spider_src are malicious?

The following RubyGems versions of spider_src are flagged malicious: 0.1.7. Treat any of these as compromised.

How do I remediate spider_src if I installed it?

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

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

Yes — spider_src is associated with the RLMA-2024-05835, RLUA-2024-10356, RLUA-2026-09412 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_src across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for spider_src (version 0.1.7).

Malicious package

spider_srcRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in spider_src (RubyGems)

MAL-2024-7030

Immediate action

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

gem uninstall spider_src

Malicious versions

1 flagged

0.1.7

Indicators of compromise (SHA-256)

50eb980f4bd3221816b750014eba984ff9823760893916cb0addc76d8edcd2dd

7d21278acdcc1cac53510dad2ab7ca79a35dd787b0996c041335e99253a09791

dcb0d417c6e926a0bb33338bd39ba62b4d1080c350721ce66c1807fbb46d498b

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05835RLUA-2024-10356RLUA-2026-09412

References

Credits

ReversingLabs · finder

Detect & block this

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