AI-powered phishing is slipping past email filters. Here's how to catch it after the click.

Key points

• AI writing tools are helping criminals produce phishing emails, fake messages designed to trick staff into handing over passwords, that read as cleanly as a real colleague's note.
• Traditional email filters, the software that scans inboxes for spam and scams, miss more of these because the usual giveaways (bad grammar, clumsy phrasing) are gone.
• Managed service providers (MSPs), the outside IT firms that run technology for small and mid-sized companies, are being pushed to watch identity and endpoint activity, not just the inbox.
• Signs of a successful phishing attack often show up as odd sign-ins, new inbox rules, or unusual file access minutes to hours after the click.
• Multi-factor authentication (MFA), a second check on top of a password, still blocks most of these takeovers when it is switched on and phishing-resistant.

Phishing used to be easy to laugh at. The typos. The Nigerian prince. The email from "Micosoft Support" asking you to log in via a link that clearly went to Russia.

That era is closing. Generative AI has handed criminals a competent copywriter, a translator, and a tireless researcher, all for the price of a chatbot subscription. The result is a phishing email that sounds like your CFO on a Tuesday morning, because the attacker fed the model three of her real LinkedIn posts before pressing send.

Email filters are struggling. And as BleepingComputer noted in coverage of the trend, the response from the managed service provider world (the outside IT firms many businesses rely on) is to stop treating the inbox as the last line of defence.

Why are AI phishing emails harder to block?

Because the tells are gone. Older filters looked for broken English, suspicious phrasing, and known-bad templates. An AI-written lure has none of that, and it can be personalised per recipient in seconds.

Attackers now scrape a target's public profile, feed it into a model, and generate an email that references the right project, the right vendor, and the right tone. The link inside still leads to a fake login page. But the wrapper around it looks entirely normal.

Some campaigns skip the link altogether. They ask the recipient to reply, start a conversation, and only later steer them toward a malicious document or a phone call. Filters that grade a single message in isolation have very little to work with.

What should MSPs and IT teams watch instead?

Identity and endpoint signals. Once a filter misses a phish, the next chance to catch it is the moment the stolen password gets used, or the moment the attacker starts poking around inside the account.

The useful signals cluster into a few areas:

None of this is exotic. Microsoft Entra ID, Google Workspace, and most endpoint tools already emit these logs. The gap is usually that nobody is reading them at 2am on a Saturday.

Would MFA have helped?

Mostly, yes, but not the cheap kind. SMS codes and app push notifications can be phished in real time using attacker-in-the-middle kits that relay the code as the victim types it. Phishing-resistant MFA, meaning passkeys or hardware security keys built on the FIDO2 standard, blocks that trick because the credential is bound to the real website's address.

For small businesses that cannot roll out hardware keys tomorrow, number-matching push and conditional access rules (which block sign-ins from unexpected locations or devices) close most of the gap.

What ordinary staff can do

Slow down on anything that creates urgency, especially around payments, password resets, or gift cards. Verify unusual requests through a second channel, a phone call or a walk to someone's desk, before acting. If you clicked something and only realised after, tell IT immediately. The first hour is when containment is cheap.