Which versions of spiderai are malicious?

The following PyPI versions of spiderai are flagged malicious: 0.0.1, 0.0.2, 0.0.3, 0.1.0, 1.0, 1.1. Treat any of these as compromised.

How do I remediate spiderai if I installed it?

spiderai is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed spiderai — how do I know if it already compromised me?

If spiderai was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is spiderai part of a known attack campaign?

Yes — spiderai is associated with the 2024-09-spider-ai 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 spiderai across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for spiderai (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging spiderai across your stack and pipelines.

Malicious package

spideraiPyPI

Malicious code in spiderai (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2024-12348

Immediate action

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

pip uninstall spiderai

What this malware does

Every time the user sends a message to the AI, the user IP, message as well as the response are exfiltrated to a hardcoded telegram channel. This behaviour is not mentioned in the package description. Instead, the description lures to offer advanced features.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2024-09-spider-ai

Reasons (based on the campaign):

exfiltration-generic
A Telegram webhook is used to send collected data.
action-hidden-in-lib-usage

Malicious versions

6 flagged

0.0.10.0.20.0.30.1.01.01.1

Indicators of compromise (SHA-256)

86e785eb3d3658362adfb50a2e5f208eb0ab70566be5cb667a0f7691a158e084

cfee8e74f278d45135c11ee4ff3f18180cb2423e333934a8ba994f5e8ec48b9a

afdb5d287f507d5c48202049dded6c2f010c1d87128b59950489e2bea6f7ea95

7744441e1e1328aa6b8597c4a433ffa12f32a8792ea550dd3efdd5a12e3fb49b

e3ad44ba2c1357aa246e854f387c52572a7702d3e31000af6044e0445d317102

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for spiderai (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging spiderai across your stack and pipelines.
If you installed it — respond
spiderai is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If spiderai was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks spiderai before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. spiderai on PyPI has been identified as a malicious package (versions 0.0.1, 0.0.2, 0.0.3, 0.1.0, 1.0, 1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2024-09-spider-ai

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks spiderai-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring