Which versions of pydefender are malicious?

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

How do I remediate pydefender if I installed it?

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

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

Yes — pydefender is associated with the 2025-02-pydefender 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 pydefender 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 pydefender (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 pydefender across your stack and pipelines.

Malicious package

pydefenderPyPI

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

MAL-2025-191833

Immediate action

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

pip uninstall pydefender

What this malware does

setup.py is prepared to download and run an obfuscated batch script. While the script is not detected by any AV currently, in the sandbox analysis it reveals behaviour like adding exclusions to Windows Defender

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

Campaign: 2025-02-pydefender

Reasons (based on the campaign):

Downloads and executes a remote malicious script.
malware
The package overrides the install command in setup.py to execute malicious code during installation.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

47fde0731c15c3a884ceb4dd40deb651eb2998414cf1eadac95c58a0f4d132bb

a1e2cc2d94eff74e302118c35c34f87e76175fe507facbe21c29883960c8223e

2df02a7ddd673cba32eb57e59dbffb385ec1c30f1c8d7e688472a17b5a18b62b

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 pydefender (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 pydefender across your stack and pipelines.
If you installed it — respond
pydefender 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 pydefender 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 pydefender 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. pydefender 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-02-pydefender

References

Credits

Kamil Mańkowski (kam193)

Detect & block this

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