extuno
PyPI packages, inspected at install time.
A poisoned PyPI release can execute code from setup.py or an import hook. Extuno diffs each version and runs it in a sandbox - with static, dynamic, and AI analysis on every scan.
pypi package
Every finding is backed by evidence.
Each finding names the change, why it is dangerous, and the recommended action.
setup.py execution
Code in setup.py runs during pip install and reaches outside the package.
Typosquat payload
A near-name package carries an exfiltration routine in its import hook.
New install dependency
The release pulls an extra dependency that opens a network socket.
Install-time code, caught before pip runs it
Extuno executes setup.py in a sandbox and records the network call it makes.
- + Vulnerability and secret-leak testing on every version
- + Static analysis reads the package without running it
- + Dynamic sandbox runs it live and records behavior
- + AI code analysis reads the full source and correlates the change against prior versions
Scan your first PyPI package free.
Your first 5 credits are free - that is 5 full scans, no card required.
Common questions
Does Extuno support PyPI?
Yes. Extuno scans PyPI with static analysis, a dynamic sandbox, and AI code analysis, and diffs every version to catch one that was clean but poisoned through an update.
How does Extuno scan PyPI?
Extuno acquires the published PyPI artifact, reads it statically with 1100+ rules, runs it in a network-segmented sandbox, reviews the source with AI, and diffs it against the prior version - naming the file, the change, why it is dangerous, and the fix.
What does Extuno catch in PyPI?
Leaked secrets, obfuscated or malicious code, dangerous permissions and APIs, exfiltration and command-and-control behavior, and the headline signal: a version that turns malicious after an update.
