2FA Enforcement for TestPyPI
What's changing?
Starting today, all users must enable 2FA before they can perform any management actions on TestPyPI.
This change is in preparation for the scheduled enforcement of 2FA on PyPI at the end of 2023.
The PyPI Blog
Incident Report: User Account Takeover
What happened?
A PyPI user's account was taken over and used to remove the user's ownership of 4 projects. This was not a malfunction of PyPI or using any vulnerability, rather the user's account was not sufficiently protected against account takeover.
The attacker added themselves as a collaborator to these projects, and removed the original owner. None of the projects had any modifications made to them other than ownership changes.
Security Audit Remediation: cabotage
This is part three in a three-part series. See part one here, and part two here.
This post is a deeper dive into the remediation of the security audit findings for cabotage - the codebase that deploys PyPI and its supporting services such as conveyor, camo, and inspector.
Security Audit Remediation: Warehouse
This is part two in a three-part series. See part one here, and part three here.
This post is a deeper dive into the remediation of the security audit findings for the Warehouse - the main codebase for PyPI.org.
The audit report can be found here. I highly recommend reading that for the fullest context first.
PyPI has completed its first security audit
This is part one in a three-part series. See part two here, and part three here
We are proud to announce that PyPI has completed its first ever external security audit. This work was funded in partnership with the Open Technology Fund (OTF), a previous supporter of security-related improvements to PyPI.
Inbound Malware Volume Report
Background
The current PyPI security reporting procedure
directs reporters to send an email to security@pypi.org with details.
security@ was previously an email alias for admin@,
a Google Group that contains all current PyPI Administrators (4 people).
GitHub now scans public issues for PyPI secrets
Back in 2019 we kicked off efforts to integrate with GitHub secret scanning. Due to the complexity in nature, the completed integration launched in 2021, with the volunteer-led effort by Joachim Jablon (@ewjoachim) and the GitHub team.
2FA Enforcement for New User Registrations
What's changing?
Starting today, newly registered users must enable 2FA before they can perform any management actions on PyPI. This change comes after we've also added a rule for accounts to have a verified, primary email address for the same set of management actions.
As a reminder, PyPI has supported adding 2FA since 2019.
PyPI hires a Safety & Security Engineer
👋 Hi there! I'm Mike Fiedler (@miketheman) I've been a Python Package Index (PyPI) contributor since early 2021, and became a maintainer in 2022. Now I'm joining the PSF to work on PyPI full-time as the first PyPI Safety & Security Engineer.
Deprecation of bdist_egg uploads to PyPI
PEP 715, deprecating bdist_egg/.egg
uploads to PyPI has been
accepted.
We'll begin the process of implementing this today.
Please note that this does NOT remove any existing uploaded eggs from PyPI.