AI Pulse · AI Trends Pulse

A report that Baseten’s production GitHub environment was taken over in 25 minutes is spreading quickly through both developer and security circles. The story centres on a personal access token, often called a PAT, which is a credential that can give automated tools or individual users access to GitHub resources. You can read the original report, but the broader lesson does not depend on the specifics of one company.

For an operator, this is a reminder that a source-code platform is not just where developers store files. It can be connected to production systems, deployment pipelines, customer-facing applications, and internal secrets. If an attacker gets access through a token with broad permissions, the time between access and real business risk can be very short. In this case, the reported 25-minute window is what has caught people’s attention.

The practical question for leadership is simple: do you know which tokens can reach production, who owns them, what permissions they have, and whether they are still needed? Teams should treat long-lived credentials, inactive accounts, and overly broad access as operational risks, not just IT housekeeping. This is also the kind of thing we build into an AI command centre, giving leaders a clearer view of the systems, access, and signals that need attention.