AI News Β· Edition 38 Β·
The attackers got cheaper before your defences did
Anthropic's fourth disclosed misuse case says less about clever machines than about how cheap ordinary attacks have become, and how late anyone notices.
The one that matters
Anthropic found a fourth case of its AI used in an attack β its own earlier review had missed it
Anthropic has disclosed a fourth cybersecurity incident involving an early version of its Claude model. The number is not the interesting part. The interesting part is that this one was found late: an earlier internal review covered the same ground and did not catch it. The company went back, found it, and said so.
That is genuinely all the public reporting supports. It does not say who was attacked, in which country, what was taken, or what it cost anyone. If you read a write-up that fills in those blanks, the write-up is guessing.
What this actually means for your business
It does not mean a machine is hunting your servers. It means the labour cost of an ordinary attack keeps falling. The attacks that hurt a 600-student school or a 30-bed clinic have never been clever. They are a fake fee-payment notice to 400 parents. They are an email that looks like it came from the principal asking accounts to release a payment before Friday. They are a supplier invoice at a 40-person workshop, correct in every detail except the bank account number at the bottom.
Those attacks used to need a person who could write clean English or clean Hindi, research your staff list, and keep track of replies. That person was the bottleneck. Software that drafts, researches and replies removes the bottleneck. So expect the same attacks, better spelled, referencing your actual vendor names, arriving in larger volume. Nothing about the defence changes. The odds of you being tried at all go up.
What it does not mean, and who is overstating it
Two groups are inflating this in opposite directions. Security vendors will use it to sell "AI-powered threat detection" to businesses that have not yet turned on two-factor authentication β that is selling a lock for the roof while the front door is open. On the other side, commentators will present this as proof that these systems are already beyond anyone's control. A missed-then-found review does not show that. It shows the ordinary thing: monitoring at these companies is imperfect and disclosure lags reality.
The useful takeaway is narrower and more durable. Every AI vendor's safety assurance is a claim about what they have detected so far, not a guarantee about what happened. Treat it the way you would treat a supplier's own quality report.
What a sensible owner should do this month
- Turn on two-factor authentication for every email account, starting with accounts, admin and the owner. It is already included in Google Workspace and Microsoft 365. Cost: one afternoon of your IT person's time.
- Write down one rule about bank details: any request to change a supplier's or employee's account number is verified by phone, on a number you already had on file, never the number in the message. Free. This single rule prevents the most expensive thing that happens to firms your size.
- Test a restore, not a backup. Pick one file from last month and actually recover it. A morning of your own time, or roughly βΉ10,000ββΉ20,000 / CAD $200β$400 for a contractor's day.
- Close the accounts of people who left and kill shared logins where three staff use one password.
- Put half a page on the wall: who to call, in what order, if money moves wrongly or systems lock up.
None of that is about AI. That is the point. The threat got cheaper to produce; the defence did not change, and most businesses still have not done it.
Also worth knowing
How this briefing is put together
Every morning we read the dayβs AI announcements and reporting from the companies themselves and from the technology press, then pick the handful that actually change something for a working business. The analysis is ours and it is written for owners and managers, not engineers. Every story links to its original source β read them, and disagree with us where weβve got it wrong.