The Attacker Doesn't Need Your Bugs

TeamPCP didn't hack GitHub. They hacked a VS Code extension. The extension had access to a developer's credentials. The credentials had access to internal repositories. GitHub became the amplifier. This is the pattern of 2026, and it keeps repeating because nobody owns the full chain. In April, a Context.ai employee got infected with an infostealer. Context.ai had an OAuth integration with a Vercel engineer's workspace. From there: Vercel's internal systems, affecting accounts belonging to OpenAI, Stripe, and McDonald's. Vercel didn't have a vulnerability. Context.ai did. The Verizon DBIR published this week puts numbers behind the pattern: third-party breaches rose 60% year-over-year and now account for 48% of all incidents. The breach isn't coming from your code. It's coming from the tools, extensions, and integrations that have access to your code. And on the defensive side, Glasswing found 10,000+ high- and critical-severity zero-days in the open source libraries that everything runs on, but only 97 have been patched. The patch queue itself is the bottleneck. Every application depending on those unpatched libraries is an amplifier-in-waiting. Securing your own software is necessary but no longer sufficient. Your security posture isn't what you built. It's the weakest thing in your stack that has access to what you built. And right now, the VS Code Marketplace doesn't gate updates. npm auto-installs postinstall scripts. OAuth tokens carry permissions their issuers forgot about. Every one of those is an assumption that stopped being true this year.