Which versions of selenium-spider are malicious?

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

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

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

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

Yes — selenium-spider is associated with the RLMA-2024-05827, RLUA-2024-10348, RLUA-2026-09135 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 selenium-spider across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for selenium-spider (version 0.1.2).

Malicious package

selenium-spiderRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in selenium-spider (RubyGems)

MAL-2024-7022

Immediate action

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

gem uninstall selenium-spider

Malicious versions

1 flagged

0.1.2

Indicators of compromise (SHA-256)

8f40bb1aa5c2f71b4bef65d0f64e9c5dd4a534fbefd8074524c17e3f7def89ba

531bb7e2c8deda4f957b5a204b05d07a0b9df49edef62b0b7607dd26ec5ea5f6

43060a9ebd61442cd7a5c149db98fdf5fbc566864b7248ef53044460efbb29c2

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05827RLUA-2024-10348RLUA-2026-09135

References

Credits

ReversingLabs · finder

Detect & block this

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