Which versions of python-uvicorn are malicious?

The following PyPI versions of python-uvicorn are flagged malicious: 0.35.0, 0.35.1, 0.36.0, 0.36.1. Treat any of these as compromised.

How do I remediate python-uvicorn if I installed it?

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

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

Yes — python-uvicorn is associated with the 2025-07-python-uvicorn 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 python-uvicorn 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 python-uvicorn (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging python-uvicorn across your stack and pipelines.

Malicious package

python-uvicornPyPI

Malicious code in python-uvicorn (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-191842

Immediate action

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

pip uninstall python-uvicorn

What this malware does

Malicious copy of uvicorn package with added healthcheck endpoint that exfiltrates application settings/env vars

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

Campaign: 2025-07-python-uvicorn

Reasons (based on the campaign):

clones-real-package
action-hidden-in-lib-usage

Malicious versions

4 flagged

0.35.00.35.10.36.00.36.1

Indicators of compromise (SHA-256)

9828112ea544c22486327053a0f6d83a5cc266162c45ad7f04e7976d4957e633

5396386b3e45bc2cc83befa80cc1843f6d8374728a22274ffbbc124319ddc16d

38823212e4bbaa76994c242265f4194ea97d0769628a0b4b6ddf9e914c107bb8

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 python-uvicorn (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging python-uvicorn across your stack and pipelines.
If you installed it — respond
python-uvicorn 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 python-uvicorn 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 python-uvicorn 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. python-uvicorn on PyPI has been identified as a malicious package (versions 0.35.0, 0.35.1, 0.36.0, 0.36.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2025-07-python-uvicorn

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193)

Detect & block this

O3 blocks python-uvicorn-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