Which versions of murmuring-spider are malicious?

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

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

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

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

Yes — murmuring-spider is associated with the RLMA-2024-05801, RLUA-2024-10322, RLUA-2026-08613 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 murmuring-spider across my projects, lockfiles, and CI pipelines?

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

Malicious package

murmuring-spiderRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

murmuring-spider is a confirmed malicious RubyGems package (MAL-2024-6995) 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 murmuring-spider (RubyGems)

MAL-2024-6995

Immediate action

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

gem uninstall murmuring-spider

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

bcdc62e9f17b4f565c997ad3347e460c43b8f1026bbe95555ad4c7c6a550bcf0

85076e78b19b556389bd1b23349c7b9920170c5e4532284f4438bcce09770203

742b018fff5640973d63569b953b55ba03bd88fbcb1e5b3941fd066c4698e3fb

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for murmuring-spider (version 0.0.2).
If you installed it — respond
Remove murmuring-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 murmuring-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. murmuring-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-05801RLUA-2024-10322RLUA-2026-08613

References

Credits

ReversingLabs · finder

Detect & block this

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