Skip to content
AI SECURITY DESKPractical intelligence for small business

Email Security

The $40,000 Email That Looked Completely Normal: How to Spot AI Phishing Before You Pay

A familiar sender and polished writing can hide invoice fraud. Use independent verification, safer payment approvals, and a practical email security checklist before you pay.

· admin

OWNER BRIEF / EMAIL SECURITY

The old clues are fading. The protection that still works is not better intuition—it is a better approval process.

Samantha Pinder runs Montgomery Tank in Grant Parish, Louisiana. Her company had worked with the vendor for years. When the invoice arrived through that familiar relationship, nothing about it demanded a second look; $40,000 went out like any other payment. Only later did investigators say the vendor’s email had been compromised. Grant Parish Sheriff Steven McCain’s office followed the money into Alabama. ATM surveillance allegedly showed Pamela Spracklen Smith, 61, of Decatur, making repeated cash withdrawals, and some proceeds were traced to Bitcoin accounts. Smith faces two counts of theft over $25,000 and two counts of computer fraud.[1]

After years working in security, here is the advice I give business owners: the most dangerous phishing email may not look suspicious at all. Inside a vendor’s compromised mailbox, the attacker inherits the timing, context, and trust of a real conversation. The message is fake; everything around it feels real.

What has changed is the cost of making that message believable. Artificial intelligence can clean up grammar, copy tone, summarize public information, produce variations, and tailor a request to a job role. It reduces the time and skill required to make the scam look like ordinary work.

THE 30-SECOND TAKEAWAY

AI phishing often looks normal.

Here is the rule I want you to remember: stop evaluating only the message. Evaluate the action it asks you to take. If it moves money, changes payment details, resets access, reroutes payroll, buys gift cards, or releases sensitive information, verify it through a separate, known-good channel before acting.

The numbers in context
Measure Finding Scope
Click-through rate 12% generic; 54% AI; 54% expert; 56% AI with human One 101-person experiment [2]
Business email compromise $3.047 billion; 24,768 complaints 2025 FBI reported losses [15]
AI-referenced scams Nearly $893 million; 22,364 complaints Multiple scam types, not phishing alone [3]
Phishing attacks 3.8 million 2025 APWG observations [16]
AI signals 82.6% KnowBe4 dataset [4]
Compromised-account attacks 57.9% increase getting through detection KnowBe4 dataset [4]
Small and medium business breaches 7,152 confirmed breaches Verizon dataset; fewer than 1,000 employees [5]

Sources: controlled experiment [2] FBI 2025 report [15] APWG [16] KnowBe4 [4] Verizon [5]

No single metric should be treated as a measure of “AI phishing.” The clearest picture still comes from four different lenses: a controlled click experiment, FBI complaint data, industry-wide phishing observations, and vendor telemetry. Read them side by side—not add them together.

Understanding The Broader Context Matters

  • AI personalization erased the quality gap in one test. Generic messages drew a 12% click rate; fully automated AI messages and human-expert messages each reached 54%, while AI with a human reached 56%. That is one 101-person experiment, not a universal employee click rate.
  • Business email compromise remains a multi-billion-dollar loss channel. IC3 recorded 24,768 BEC complaints and $3.047 billion in reported 2025 losses—about $123,000 per complaint on average. The average is arithmetic, not a prediction of what a typical victim loses.
  • The FBI’s AI number is broader than phishing. The 22,364 AI-referenced complaints and nearly $893 million in losses span multiple scam types. It shows AI’s fraud footprint, not an AI-phishing subtotal.
  • Observed phishing volume stayed enormous. The Anti-Phishing Working Group observed 3.8 million phishing attacks during 2025. That is an industry observation count, not the number of victims.
  • Vendor telemetry points to automation and trusted-account abuse. KnowBe4 reported AI signals in 82.6% of the phishing emails it analyzed and a 57.9% increase in attacks sent from compromised accounts getting through traditional detection. Those percentages describe its own dataset, not all email worldwide.
  • Small businesses appear in real breach data. Verizon counted 7,152 confirmed breaches in its small- and medium-sized business dataset; credentials were compromised in 31% and phishing appeared in 9% of recorded initial-access paths. Verizon defines this group as organizations with fewer than 1,000 employees.

Real businesses lost money to believable requests

These are not stories about people who missed obvious spelling errors. Each case exploited a normal business reflex: pay a known vendor, follow an executive’s request, or respond to an official-looking notice.

A known vendor. A real invoice. A changed destination.

$40,000 sent

Montgomery Tank paid an invoice that appeared to come through a long-standing vendor relationship. Investigators said the vendor’s email had been compromised.[1]

Break the chain: My rule is simple: confirm every new or changed bank destination by calling a number already in your records—not one supplied in the email.

Executive authority beat written policy.

$300,000 wired; funds later recovered

Vitality Institute CEO Marya Khalil-Otto said a new chief financial officer received fraudulent invoices from someone impersonating the company’s chief operating officer. The CFO did not follow company protocol. Rapid action and insurance helped recover the money.[6]

Break the chain: I tell owners to make the rule stronger than rank: even an “executive” request requires the same second-channel approval.

Official-looking notices created a false deadline.

More than 800 organizations paid

Washington’s attorney general documented solicitations made to resemble Secretary of State communications. One Bellevue owner paid $200 for a filing that cost $60 directly. A Snohomish owner said the solicitation looked official and offered no effective way to cancel.[7]

Break the chain: I would reach the agency or vendor through a saved bookmark or official record, not the message’s link or phone number.

The common failure is not intelligence. It is workflow. The message arrives at a moment when “doing the job” means paying, complying, or fixing something quickly. Any defense has to survive that moment.

Lined up, these cases reveal the same playbook—not improvisation. AI now runs that playbook faster and more convincingly. Here is how an AI phishing attack unfolds, step by step.

How the attack unfolds
Stage What the attacker does Where to interrupt it
Research Uses public business context to learn names, roles and relationships Limit public details about payment routines
The lure Creates a believable request using familiar context Check the requested action against policy
The send Delivers through an impersonated or compromised account A familiar sender is not proof
The click or action Pushes a payment, login or sensitive-data request Verify through a separate known contact
A foothold Uses stolen credentials or access Use phishing-resistant MFA and revoke sessions
Quiet control Hides activity through rules or ongoing access Review forwarding, delegates and sign-in alerts
Payday Moves money or exploits information Call the bank immediately if money moved

Break the chain: My advice is to starve Step 1 by limiting what is public about your vendors and routines — and break Step 4 by verifying every money-moving request through a separate, known-good channel.

Owner Testimonials Confirm The Risk

Owner discussions are anecdotal, not a substitute for breach statistics. Their value is practical: they show which lures are reaching real businesses and which checks people use when something feels wrong.

What owners are seeing
Reported pattern Owner response
Reddit discussions: flattering acquisition or executive outreach, sometimes aimed at businesses already dissolved [12] Verify the buyer, lender or partner before sharing financial records or opening documents
Public social warnings: urgency, secrecy and payments redirected to a supposed safe account [13] [14] Call the office using a number already in your records before changing the payment destination

These are anecdotal reports. They do not establish that AI created a particular message.

Owner-forum sources [12] [13] [14]

These posts do not prove that AI created any specific message. They reinforce the operating reality: criminals exploit routine business context, and owners need a verification step that still works when the wording looks professional.

How to spot phishing emails when the writing looks right

I no longer tell people to rely on bad grammar; it is now a weak signal. I look instead for a mismatch between the request and your normal process. One clue may be innocent; a cluster should trigger verification.

Test the request before you act
Signal What to check
Value moves New bank details, unusual wires, payroll changes, gift cards or sensitive-data requests
Pressure rises A sudden deadline, threat or urgent executive demand
Isolation Instructions not to call, to keep a secret or to use only the supplied channel
Login detour A document asks you to sign in, approve a prompt, scan a QR code or re-enter a password
Channel mismatch A vendor uses a personal account or a familiar contact changes channels unexpectedly
Almost right A similar display name paired with an unfamiliar address, domain, reply-to or destination

Stop and verify through a known contact method. One clue can be innocent; a cluster should trigger verification.

One campaign shows why I no longer trust the packaging. In its investigation of an August 2026 campaign, Microsoft found more than one million messages that impersonated executives and ServiceNow, included fabricated forwarded conversations and invoices, and sought Automated Clearing House payments around $50,000. Microsoft found indicators consistent with AI-assisted template development; it did not claim AI created every element.[8]

MINDSET SHIFT

A familiar name is not proof. A familiar thread is not proof.

In my years in security, I learned not to treat familiarity as proof. If an account is compromised, a criminal may see prior invoices, signatures, job titles, and the rhythm of a real relationship. The question is no longer “Does this email look fake?” It is “Did we independently verify the action?”

One rule stops the costliest scams

Here is the rule I would put in writing: no payment, bank-detail change, payroll change, gift-card request, or sensitive-data release is approved solely through the channel that delivered it.

Here is what I mean in practice. If the request arrives by email, verify by calling a known number. If it arrives by text, use a saved contact or a business directory you already trust. If it arrives by phone, hang up and call back through your own records. I would never use the number, link, or reply address in the request itself. The FTC and the FBI’s Internet Crime Complaint Center both recommend this kind of independent verification.[9][10]

A verification script your team can actually use

“Hi, I received a request to change the payment instructions for invoice 1842. I am calling the number already in our vendor record to confirm the change. Please verify the last four digits of the existing destination and explain why it is changing.”

I tell teams not to ask only, “Did you send this?” A compromised mailbox or an impostor on the phone can answer yes. Verify details the requester should know and compare the change against the record you already have. For large or unusual payments, require a second approver.

A 30-minute prevention plan

I do not think you need an enterprise security program to break the most common path from email to loss. I would start with five controls and assign an owner to each one.

  1. Write the verification rule. List the actions that always require a second channel: new or changed bank details, wires, payroll changes, gift cards, password resets requested for someone else, and releases of tax, customer, or employee data.
  2. Turn on multifactor authentication everywhere. Prioritize email, banking, payroll, accounting, and domain administration. Use phishing-resistant options such as passkeys or hardware security keys where available. CISA recommends phishing-resistant MFA because some one-time codes and push prompts can still be tricked or stolen.
  3. Close the mailbox back doors. Block automatic forwarding to outside addresses unless there is a documented business need. Alert on suspicious sign-ins, new forwarding rules, mailbox delegates, and recovery-method changes. Keep administrator accounts separate from everyday email.
  4. Authenticate your domain. Ask whoever manages your domain to configure SPF, DKIM, and DMARC. In plain language, these records help receiving systems check whether mail claiming to be from your domain came from an approved sender and what to do when it did not.
  5. Make reporting safe and fast. Give staff one obvious way to say “I clicked” or “I entered my password.” Do not punish early reporting. A ten-minute head start can matter more than determining who made the mistake.

This is not just my advice. CISA’s joint phishing guidance focuses on two common objectives—stealing credentials and delivering malware—and urges organizations to reduce both the likelihood and impact of successful attempts.[11]

COPY INTO YOUR POLICY

Pause. Verify. Approve.

Any request involving money, account access, payment details, payroll, gift cards, or sensitive information must be verified through a known contact method independent of the request. Exceptions require approval from two people.

What to do when your business email is hacked

I tell owners to treat signs of mailbox compromise as an incident, not a password nuisance. Warning signs include unknown sent mail, missing messages, unexpected forwarding rules, new inbox filters, unfamiliar recovery information, or vendors reporting strange requests from your address.

  • Call the bank now if money moved. Ask the financial institution to recall or freeze the transfer and contact the receiving bank. Do not wait for an internal investigation. The IC3 advises immediate bank contact after an unauthorized transfer.
  • Secure the account from a known-clean device. Change the password, revoke active sessions, remove unknown recovery methods and app access, reset MFA, and review delegated access. If the same password was reused, change it everywhere else.
  • Remove persistence. Check inbox rules, forwarding addresses, mailbox delegates, connected applications, and filters that hide replies or delete alerts. Attackers often preserve access or conceal the conversation.
  • Preserve evidence. Save the original messages, full headers when available, invoices, bank instructions, phone numbers, timestamps, and screenshots. Keep a simple timeline of what happened and who acted.
  • Warn the people in the blast radius. Tell employees, customers, and vendors who may receive fraudulent follow-ups. Use a different trusted channel if the mailbox itself is still suspect.
  • Report the incident. Submit a complaint to the FBI’s Internet Crime Complaint Center at IC3.gov. Notify your insurer and IT provider according to policy. If malware may be present, disconnect the affected device from the network and get qualified help before reconnecting it.

If personal information was exposed, your legal notification duties depend on what was compromised and where affected people live. I would not guess. Ask qualified counsel or your insurer’s breach-response team.

Your IT provider should be able to prove the controls exist

I would not accept “we manage Microsoft 365” or “we filter spam” as a control report. Ask for plain evidence. A capable provider should be able to answer these questions without hiding behind a product name.

CONTROL ASK FOR PROOF
Payment verification Who owns the written rule, and when was it tested?
MFA coverage Which accounts lack MFA, and which use phishing-resistant methods?
Forwarding rules Is external auto-forwarding blocked? Who receives change alerts?
Sign-in alerts Who reviews risky logins, impossible travel, and new recovery methods?
Email authentication Are SPF, DKIM, and DMARC configured and monitored?
Incident response Who calls the bank, disables sessions, preserves evidence, and contacts users?

I am not asking you to become a security engineer. I am asking you to make responsibilities visible. A service can be “managed” while a critical setting remains off, an alert goes nowhere, or nobody knows who calls the bank.

The bottom line

AI phishing is a process problem disguised as a message problem. After years in security, that is the conclusion I keep coming back to. Better writing and personalization make scams harder to recognize on sight. They do not make a second-channel verification rule obsolete. They make it essential.

I still teach the red flags, but I would not bet the business on everyone spotting every fake. Build a process in which one believable email cannot move money, change access, or release sensitive information by itself.

Sources

Accessed September 28, 2026. Statistics describe the cited source’s dataset or reported complaints and should not be generalized beyond that scope.

1. Montgomery Tank owner account. Wealth of Geeks, “A Louisiana Business Paid a $40,000 Invoice From a Vendor It Knew…” (2025). Open source

2. AI-personalized phishing experiment. Heiding et al., “Evaluating Large Language Models’ Capability to Launch Fully Automated Spear Phishing Campaigns” (2024 preprint). Open source

3. AI-related complaint data. FBI, “Cryptocurrency and AI Scams Bilk Americans of Billions” (April 6, 2026). Open source

4. Vendor phishing dataset. KnowBe4, “New KnowBe4 Report Reveals a Spike in Ransomware Payloads and AI-Powered Polymorphic Phishing Campaigns” (2025). Open source

5. Small-business breach data. Verizon, 2026 Data Breach Investigations Report, pp. 97–98. Open source

6. Vitality Institute owner account. Entrepreneur, “6 Leaders Share This Year’s ‘Gut Punch’ Low Moments” (2025). Open source

7. Washington owner complaints. Washington State Office of the Attorney General, deceptive texts and emails enforcement release (July 21, 2022). Open source

8. AI-assisted executive impersonation campaign. Microsoft Security Blog, “Protecting organizations from AI-assisted executive impersonation and invoice fraud” (September 10, 2026). Open source

9. Small-business phishing guidance. Federal Trade Commission, “Cybersecurity for small business: Phishing” (November 13, 2018). Open source

10. Payment-verification and mailbox controls. FBI Internet Crime Complaint Center, “Business Email Compromise: The $26 Billion Scam” (April 6, 2020). Open source

11. Phishing-prevention guidance. CISA, NSA, FBI, and MS-ISAC, “Phishing Guidance: Stopping the Attack Cycle at Phase One” release (October 18, 2023). Open source

12. Reddit owner-thread synthesis. ConsumerAffairs, “A new email scam is targeting small business owners” (July 20, 2026), reviewing examples from r/scams and r/smallbusiness. Open source

13. Facebook forum cross-check. Public Scam Alert group post summarizing recurring scam triggers (May 13, 2026). Open source

14. Small-business social account. Affordable Plumbing Solutions public warning that a hacked email account sent false invoices (September 16, 2026; archived page). Open source

15. 2025 Internet Crime Report. FBI Internet Crime Complaint Center, 2025 Internet Crime Report (published April 2026). Open source

16. 2025 phishing activity. Anti-Phishing Working Group, 2025 year-in-review release and Q4 2025 Phishing Activity Trends Report (February 23, 2026). Open source

Independent guidance for practical small-business defense.

Back to AI Security Desk