We got admin access to Baseten's production GitHub in 25 minutes

The article highlights a severe third-party and cloud supply-chain risk: a publicly accessible container registry image exposed a live GitHub personal access token with admin-level access to Baseten production and internal repositories, including systems tied to product, GitOps, and customer-specific assets. For CIOs and technology leaders, the business impact is significant—this kind of credential leakage could enable source-code theft, infrastructure tampering, or downstream customer compromise, underscoring the need for stricter vendor assurance, secrets hygiene, and continuous exposure testing across the software delivery chain. IT organizations should treat build artifacts, registries, and CI/CD histories as high-risk assets, because a single overlooked image layer or metadata field can bypass perimeter controls and create material operational and compliance exposure.