14 minutes. That's shorter than most standups and apparently long enough to empty out a whole company.
and the scariest number in this story isn't even the 14.
ok so what actually happened
This week David Kennedy, the former NSA hacker who founded TrustedSec, went on CNN's Erin Burnett OutFront and said he'd stepped away from a live incident to talk about it. One of his customers had just been hit by what he called an "agent swarm". Per IBTimes UK, the customer let him share the basics but not its name.
Here's his account, as reported by IBTimes UK, India Today and others:
- More than 30 different types of AI agents probed the company's infrastructure at the same time
- They logged in with valid usernames and passwords
- They found a flaw in how the company's application handled two-factor authentication and got past it
- They exfiltrated "a substantial amount of data", then ran ransomware that encrypted the entire file system
All of that in 14 minutes. "Never seen anything that fast before," Kennedy said on CNN.
The company didn't detect it for about four and a half hours. Its systems kept running after the encryption, then started throwing errors and restarting, and only then did staff notice an outage. By that point the attack was long over.
The clip blew up. The post on r/OpenAI was at 866 points and 145 comments when we pulled it. Cybersecurity journalist Nicole Perlroth posted on X that "we are on attackers' clocks now."
hot take: the AI part is the least surprising bit
Ngl the headline "AI bypassed 2FA" is doing a lot of work.
Read Kennedy's own words in the CNN clip. The agents "logged in with their usernames and passwords" and found "a flaw in their application" around 2FA. So the swarm didn't crack strong MFA with some spooky new math. It walked in with valid logins and poked at a buggy 2FA flow until one path worked.
He also explained how this kind of crime gets split up: some ransomware groups "phish and harvest credentials" and sell them to more capable groups that run the actual attack. That's an old business model. Very boring, very effective.
So imo the real shift is parallelism not genius. A human attacker tries one idea, waits, tries the next. Thirty agents try everything at once, and the one weak spot gets found in minutes instead of months. Security vendor Morphisec made the same point in a blog post on the incident, which yes, also pitches its own product, but the arithmetic holds up.
And the number I can't stop thinking about is four and a half hours. Attack done in 14 minutes, noticed hours later from an outage. Even a team that triaged every alert in half an hour shows up to an empty, encrypted building. lowkey the detection gap is the story here.
your agents are holding the loot fr
This is where it gets personal if you build agents.
The swarm started with credentials. That's the prize in this whole AI agent swarm cyberattack. And agents are basically credential piles with a chat window attached.
Say you've got a support agent with a Gmail token and a Stripe key sitting in an .env file, plus a config file someone copy pasted into three repos. Every one of those is a login someone can harvest and sell. If your agent can delete, refund and send, so can whoever gets its keys.
So my read on what to actually do:
- Get app keys out of your agent's hands. This is the bit we built MewCP for. App credentials sit encrypted in a vault and get injected into the request only when a tool runs, so they never reach the agent, the client or the model. The agent holds one MewCP key, and if that leaks you hit Revoke in the dashboard and it stops working right away.
- Give each agent the smallest set of tools that works. In MewCP you pick which apps and which actions each agent gets, like read and send but not delete. Anything switched off gets stopped before it reaches the app.
- Make sure something is watching that isn't a person. Kennedy's customer found out from an outage. MewCP logs every call with the tool, time, status and latency, which won't catch a hacker by itself but means you're not gonna be guessing when an agent suddenly makes 400 calls at 3am.
To be super clear, none of this would've fixed a broken 2FA flow in somebody else's app. That's on whoever wrote the auth logic. It's about not making your own agent the next set of harvested logins.
stuff we still don't know
A lot tbh. Kennedy's account hasn't been independently verified, which IBTimes UK and Morphisec both say outright. The company is unnamed. The exact 2FA flaw isn't public. We don't know how much data was taken, which AI models or tooling the attackers used, or how "30 different types of agents" maps to real software.
We also couldn't load the r/OpenAI thread itself, so no hot takes from the comments here, sorry.
What would change my mind: if the post-incident write-up shows humans drove most of it and the agents were just fast scanners, the "swarm" framing gets a lot less wild. Still a 14-minute breach though. still bad.
where this came from