Which versions of spider-html are malicious?

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

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

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

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

Yes — spider-html is associated with the RLMA-2024-05831, RLUA-2024-10352, RLUA-2026-09408 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-html across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for spider-html (version 0.1.9).

Malicious package

spider-htmlRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in spider-html (RubyGems)

MAL-2024-7026

Immediate action

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

gem uninstall spider-html

Malicious versions

1 flagged

0.1.9

Indicators of compromise (SHA-256)

e7980e79e41ad71cb247c809cf52eed4ab4275c806f0c32c54045a407eef001b

d0237d4f518c781e31dce33bb87efaa9a35c65b71567db931612162f6eaab785

11604a34d85f1c121ad44c948ce6c5a01f68fa304a73e5db8dc2d91af3963e05

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05831RLUA-2024-10352RLUA-2026-09408

References

Credits

ReversingLabs · finder

Detect & block this

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