Nicholas Moore hacked into three US government networks using stolen credentials, then bragged about it on Instagram. The same week, Fast Company published a piece on the hidden risks of vibe coding, warning that AI-generated code is being shipped into production without anyone understanding its security properties. These stories share a nervous system.

The Credential Problem Is Structural, Not Individual

Moore's hack was embarrassingly simple: stolen credentials, three networks, one Instagram flex. The Supreme Court's systems, which are supposed to represent institutional gravity and permanence, turned out to be as porous as any startup's staging environment. This is the same vulnerability that vibe coding creates at scale. When developers use Claude or GPT to generate functional code quickly, they often skip the threat modeling that would catch exactly these entry points. The speed is real. The debt is invisible until it isn't. A 2023 paper in IEEE Security and Privacy by Pearce et al. found that GitHub Copilot suggested insecure code in roughly 40 percent of security-relevant scenarios, a finding that predates the vibe coding era entirely. The number is almost certainly worse now.

Shadow Dockets and Shadow Code

The trending story about the Supreme Court's shadow docket adds a layer. Institutions are increasingly making consequential decisions in opacity, whether it's judicial procedure or software deployment. The vibe coder ships a feature without audit. The court decides a case without full briefing. Both are optimizing for speed at the cost of accountability. The Fast Company piece recommends four steps: audit, test, document, restrict. The Moore sentencing recommends probation. Neither consequence matches the scale of the underlying problem. .