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 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 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?

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

Malicious package

spyderlibPyPI

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

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
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for spyderlib (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging spyderlib across your stack and pipelines.
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 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 spyderlib 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. 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