Which versions of spyderlib are malicious?

The following PyPI versions of spyderlib are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate spyderlib if I installed it?

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

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

Yes — spyderlib is associated with the 2025-06-stubsout 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 spyderlib across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for spyderlib (version 0.0.1).

Malicious package

spyderlibPyPI

Advisory published Jun 7, 2025Updated Dec 12, 2025

spyderlib is a confirmed malicious PyPI package (MAL-2025-191877) that steals credentials and exfiltrates sensitive data (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in spyderlib (PyPI)

MAL-2025-191877

Immediate action

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

pip uninstall spyderlib

What this malware does

While described as telemetry, importing the package attempts to send out some basic info as well as quite sensitive environmental variables.

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

Campaign: 2025-06-stubsout

Reasons (based on the campaign):

The package contains code to exfiltrate basic data from the system, like IP or username. It has a limited risk.
exfiltration-env-variables

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ce3db307efc4dde887c78157dfc58c9182fc15373433443a0bb78562d9e4bc8e

5c8cd8b0bcebda767e6d2f280c42cfd952522e31086aa816be6b3350611874a1

daddd4c00e81681ff8be6f1592555499c4ef51af1a85d9879f34715fa9aa78bd

Detection & response playbook

Credential / info stealer

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

Campaign

2025-06-stubsout

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

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

Explore

All malware advisories How O3 detects malware Vulnerability database