Which versions of movie-spider are malicious?

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

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

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

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

Yes — movie-spider is associated with the RLMA-2024-05795, RLUA-2024-10316, RLUA-2026-08600 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 movie-spider across my projects, lockfiles, and CI pipelines?

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

Malicious package

movie-spiderRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

MAL-2024-6989

Immediate action

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

gem uninstall movie-spider

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

2b393c5e21301cbbecf89bdc46c7ccc416caab58058169d42aa9de0e5bda6925

5495b824510edc114228907614b1e53dd9b1670faa8cdf1b38cd7c4acf300a6b

c7ab4fe61543ddfe1fcf4698387bda39608f7db0d96584f4d8b46cf6dac1a03f

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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