pypi-supply-chain-response

To investigate a compromised PyPI package, you must identify exposure, confirm affected versions, and hunt for IOCs. This process guides you through six phases including exposure triage, version confirmation, IOC hunting, containment, credential rotation, and prevention across Python environments.

Checking for a vulnerable Python package version requires confirming exposure across your Python environments and manifests. You can generate an automated check_compromise.sh script to detect the compromised package and identify which specific versions are affected.

Responding to a PyPI supply chain attack involving transitive dependencies requires a structured incident response runbook. You can produce a full markdown document or interactive checklist to orchestrate exposure assessment, containment, and recovery from the compromised package.

You can generate a structured incident report template for a PyPI package compromise. The output includes an interactive triage checklist, a full markdown runbook, or an automated shell script to document the six-phase incident response and recovery process.

Yes, the PyPI incident response process handles credential rotation and prevention. It guides you through the final phases of supply chain incident response, ensuring compromised credentials are rotated and preventative measures are applied across your Python environments.