Which versions of dradis_ntospider are malicious?

The following RubyGems versions of dradis_ntospider are flagged malicious: 3.15.0. Treat any of these as compromised.

How do I remediate dradis_ntospider if I installed it?

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

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

Yes — dradis_ntospider is associated with the RLMA-2024-05679, RLUA-2024-10198, RLUA-2026-08017 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 dradis_ntospider across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dradis_ntospider (version 3.15.0).

Malicious package

dradis_ntospiderRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in dradis_ntospider (RubyGems)

MAL-2024-6873

Immediate action

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

gem uninstall dradis_ntospider

Malicious versions

1 flagged

3.15.0

Indicators of compromise (SHA-256)

e9895af658b20db8c8fed1e3f702a15ffa40fd07239cb340a3880fab28159b34

6a9e9794ede7c10770575e7b33c43016b520f1c1c9528599f1d7a3f1b591c8ed

757b4ce525b747ee7f0098736068552ac777c457388a78713eeff98a72079c58

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05679RLUA-2024-10198RLUA-2026-08017

References

Credits

ReversingLabs · finder

Detect & block this

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