Claude, GPT and the Minnesota attackers all used known bugs and weak logins

Claude, GPT, and the Minnesota attackers all relied on the same class of failures: known bugs and weak logins. The piece arguing that point, Use It or Lose to It on Cabreza’s Substack, was also shared on Hacker News under the Claude/Codex/Fable thread. The claim is not that these actors shared tooling or intent. It is that each path of abuse leaned on defects and access controls that defenders already knew how to close.

On the technical side, the pattern is ordinary rather than exotic. Known bugs are issues that already have public discussion, patches, or workarounds; weak logins are credentials, password policies, or account hygiene that fail basic checks. Those two surfaces still open production systems because they sit outside the flashy layer of novel exploit chains. Agents and human attackers alike can walk in through unpatched software and soft authentication long before they need advanced capability.

For engineers and builders, the practical signal is prioritization. If models and attackers both succeed by reusing known bugs and weak logins, security work that stays stuck on speculative threat models while leaving patch debt and identity debt open is mis-aimed. Builders shipping AI-assisted workflows should treat agent access the same way they treat any privileged automation: least privilege, hard auth, and a backlog that actually retires known issues.

The competitive and market context is that capability gaps between AI tools matter less here than operational gaps between teams. A product stack that patches and enforces strong login practices is harder for both a language model–driven actor and a conventional attacker to abuse. Teams that market sophistication while leaving basic hygiene unfinished remain exposed regardless of which brand of model sits on the other side of the wire.

The takeaway is concrete: inventory known open bugs and weak login paths first, then measure how much of your attack surface those two categories still cover. Watch whether AI-related incident writeups keep pointing at the same boring failures—unpatched software and soft credentials—because that is the shared mechanism the Cabreza framing highlights, not a new class of zero-day.