How to fix: PyPI token in source
pypi-AgEIcHlwaS... tokens allow uploading packages.
Why it matters
An exposed PyPI token allows an attacker to upload a malicious version of any Python package associated with the token, injecting arbitrary code into the install process for every user that runs pip install on that package.
pypi-AgEIcHlwaS... tokens allow uploading packages.
How to fix it
- 1Revoke the token immediately via PyPI account settings → API tokens
- 2Audit recent package uploads for your account
- 3Create a new token scoped to specific projects (not the whole account)
Code examples
GitHub Actions: use PyPI Trusted Publisher (no token needed)
# Use OIDC-based Trusted Publishers instead of tokens
jobs:
publish:
permissions:
id-token: write # Required for OIDC
steps:
- uses: actions/checkout@v4
- run: python -m build
- uses: pypa/gh-action-pypi-publish@release/v1
# No password/token needed: OIDC handles auth.pypirc: never commit this file
# ~/.pypirc (user-level, never commit to source control)
[pypi]
username = __token__
password = pypi-AgEIcHlwaS...
# Add to .gitignore:
# .pypircReferences
Detected automatically by VulnRadar. The check id is secret-pypi-token, stable across every scan so you can filter or diff on it.
More secrets checks
- CriticalStripe webhook signing secret in client bundle
- MediumGoogle Maps API key in source
- CriticalGoogle OAuth client_secret in source
- LowFirebase API key (public) in source
- CriticalAWS Secret Access Key in source
- CriticalGitHub PAT in source
- CriticalNPM auth token in source
- HighCloudflare API key in source
Questions
- How severe is PyPI token in source?
- VulnRadar rates this critical severity in the secrets category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id secret-pypi-token, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does PyPI token in source map to?
- It maps to CWE-798. In the OWASP Top 10 it falls under A07:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.