Which versions of spider-monkey are malicious?

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

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

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

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

Yes — spider-monkey is associated with the RLMA-2024-05832, RLUA-2024-10353, RLUA-2026-09409 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-monkey across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for spider-monkey (version 0.0.11).

Malicious package

spider-monkeyRubyGems

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

Malicious code in spider-monkey (RubyGems)

MAL-2024-7027

Immediate action

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

gem uninstall spider-monkey

Malicious versions

1 flagged

0.0.11

Indicators of compromise (SHA-256)

693f927fe4266bee69c1a11bd9a669eecb45d0f42eeceea8c633f4aa1b309a7f

9dcefac4ee4b34416691207a263801c79de8a2d910c72dd2596f0f0d0e9fdf2a

6bb1e2e12e85d5528014de44ee8967c886a91ff97fa67118870fa8e3ec7b5c2c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05832RLUA-2024-10353RLUA-2026-09409

References

Credits

ReversingLabs · finder

Detect & block this

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