AI & Email Security

One Hidden Instruction Can Make Your AI Report a False Invoice

A prompt injection email is a message with instructions hidden inside it that your AI assistant reads and follows, while you see a completely normal email. The AI is not tricked into clicking anything. It is tricked into telling you something false — and new research shows exactly how.

5x
The false invoice amount vs. the real one in Forcepoint's test
10 of 10
Test runs where the AI summary reported the false amount and date
Plan 2
The Defender for Office 365 tier that detects it — many SMBs don't have it
Published September 3, 2026 Simpatico Systems AI & Cybersecurity 7 Min Read

Can one hidden instruction in an email make your AI assistant report something false to you? Yes, and researchers have now shown exactly how.

In a test published August 25, 2026, Forcepoint's X-Labs team planted invisible instructions in an email and had an AI summarizer read it inside Microsoft Outlook. The real invoice in the message was for 46,200 euros, due August 21, 2026. Every summary the AI produced reported 231,000 euros, due September 3 at 14:00. Five times the amount, on a deadline that did not exist. It worked in all 10 runs.

The reader saw nothing unusual. The instructions that caused it never appeared in the summary.

Key Takeaways

  • Forcepoint X-Labs demonstrated on August 25, 2026 that hidden text in an email caused an AI summarizer to report a false invoice amount (231,000 euros vs. the real 46,200) and a false due date — in 10 out of 10 runs.
  • The hidden instructions were styled invisible to the human reader and never appeared in any summary, so nothing signaled the message had been tampered with.
  • Prompt injection targets the AI reading your mail, not you — normal phishing training teaches staff to spot what looks wrong, and this attack is built to look completely normal.
  • Microsoft Defender for Office 365 Plan 2 now detects prompt injection in inbound email with no configuration needed — but Plan 1 and Business Premium tiers don't include it, and nothing announces the absence.
  • The single control that catches this cold: no payment amount, bank detail, or due date ever changes based on an email or an AI summary — verification happens by phone on a number you already had.
  • The exposure isn't just Copilot: browser extensions, CRM assistants, and no-code automations that read your inbox all receive the same raw message a human never sees.

What Is Prompt Injection in Email?

Prompt injection means putting instructions inside content an AI reads, so the AI follows those instructions instead of the ones it was given. In email, the content is the message: the subject, the body, a quoted reply chain, an attachment, or markup you never see.

Here is the mechanic that makes it work. When you ask an assistant to summarize an email, it does not receive a picture of what your screen shows you. It receives the raw message, all of it, including anything hidden in the HTML. To the model, attacker-written text and legitimate text look the same. There is no formatting that says "this part is data, ignore any orders in it."

Microsoft describes the difference from ordinary phishing plainly: traditional phishing targets the human reader and succeeds when a person clicks, while prompt injection targets the AI model reading on that person's behalf and succeeds when the model follows the injected instruction.

That is the shift worth sitting with. Every piece of security training your staff has had is about spotting something that looks wrong. This one is invisible to them by design.

How Did the Forcepoint Test Work?

The hiding technique is almost insultingly simple. The researchers added text styled with zero font size, zero line height, and white color. In Outlook it renders as nothing at all. In the raw message the AI reads, it is ordinary text. The results, across 10 runs each:

Clean Email: 10 for 10 Correct

The unmodified version of the email produced an accurate summary in every run — right amount, right date, right names.

Injected Email: 10 for 10 False

The tampered version produced the false amount (231,000 euros) and the false date (September 3) in every single run.

A Real Name Disappeared

Diego Siciliani, present in the real email and every clean summary, was missing from every injected one.

No Trace in the Output

The hidden instructions themselves never showed up in any summary, so nothing signaled the message had been tampered with.

That last point is what makes this different from a bad AI answer. A hallucination is random. This was deterministic, repeatable, and directed by someone else.

Now think about who gets an email with an invoice amount and a due date. Accounts payable. A bookkeeper. An office manager. The person most likely to be handed an AI summary tool to save time, and least likely to open the raw HTML to double-check it.

Why Hidden Text Works When a Human Cannot See It

Because the two of you are reading different documents. Your email client renders the message: it applies the styling, hides what is set to zero size, and shows you the result. The AI assistant, in most setups, gets handed the source instead. Everything the renderer threw away is still in there.

"Extract the text that is actually presented to the user and pass that to an LLM ... treat any retrieved content as untrusted."

In plain terms: feed the AI what the human sees, and never let a message it read give it orders. That is good advice for whoever builds the tool. It is not something you can do from inside your own inbox, which is why the fix has to come from somewhere else — this is exactly the kind of gap our cybersecurity team checks for in a client's actual mail environment, not just their policy documents.

Is Microsoft Copilot Email Summary Safe from This?

Safer than it was, and not on its own. This is worth being precise about, because it is where the practical answer lives.

Microsoft 365 Copilot has its own protections that run at the moment the model executes: input filtering, prompt design that separates your instructions from message content, limits on what the model can reach, and output filtering.

The newer piece sits earlier in the chain. Microsoft Defender for Office 365 Plan 2 now detects prompt injection content in inbound email before it reaches a mailbox or an assistant, as part of the same filtering that already catches phishing and business email compromise. The documentation was published August 6, 2026. Three things about it matter for a small business:

No Configuration Required

If you have Plan 2, it is running. There is no switch to flip and no policy to build.

It Reads Like the AI Reads

It inspects the message the way an assistant would receive it — hidden and off-screen text, quoted and forwarded content, and encoded segments normalized before analysis.

Visible in Your Tooling

Detections land under the High confidence phishing verdict with a detection technology value of "Prompt injection protection," filterable in Threat Explorer and Advanced Hunting.

It Covers Every Reader

Because filtering happens in the mail channel rather than inside one assistant, it protects whatever reads the mailbox: Copilot, a third-party add-in, or a homegrown automation.

The catch is in the name. Plan 2. A large number of small businesses are on Microsoft 365 Business Premium or a Defender Plan 1 tier and do not have this, and nothing in their admin center announces the absence. That is the specific gap worth checking this week.

What Does This Mean for Law Firms Specifically?

Two extra pressures on the same problem.

A law firm's email carries settlement figures, filing deadlines, wire instructions for a real estate closing, and client instructions. An AI summary that quietly reports the wrong date is not an inconvenience there. Missing a filing deadline because the summary said the third instead of the twenty-first is malpractice territory, not an IT ticket.

And the timing is awkward. Firms are adopting AI faster than they are governing it. Clio's 2025 Legal Trends Report found 53% of legal professionals say their firm has no AI policy or are unsure whether one exists, while 82% plan to increase their AI use in the next 12 months. Meanwhile California's SB 574 would put attorney AI duties into state law, enforced through court sanctions and bar discipline. A firm that cannot say which tools read its mail is going to have a hard time with any of that.

What Should a Small Business Actually Do About It?

Five things, roughly in order of how much they buy you.

Find Out Which Defender Plan You Are On

Not which bundle you think you bought. The actual license. If you are not on Defender for Office 365 Plan 2, you do not have the mail-layer protection described above, and that is a licensing conversation with a real answer.

Make One Rule About Money and Never Break It

No payment amount, bank detail, or due date changes based on an email, an AI summary of an email, or both. Verification happens on a phone number your business already had on file. This rule predates AI, and it is the single control that would have caught the Forcepoint scenario cold — the false invoice still has to get paid by a person.

Tell Your Staff This Specific Thing Exists

Most security training is "look for what seems off." This attack is built to seem fine. Say the sentence out loud to your team: the AI summary is a convenience, not a source of truth, and for anything involving money you open the actual email.

Know Where AI Is Reading Your Mail

Copilot is the obvious one. Browser extensions that summarize your inbox, CRM tools with an AI assistant attached, and no-code automations somebody set up are the ones that never got reviewed. Each is another reader of your mail with the same blind spot.

Turn On the Boring Stuff

Multi-factor authentication, DMARC, DKIM, and SPF, so it is harder to send you a convincing message in the first place. None of this is new advice. It is just newly relevant, because a well-formed injected email that clears your filters gets read by a machine that cannot be suspicious.

Frequently Asked Questions

What is a prompt injection email?
It is an email containing instructions aimed at an AI assistant rather than at you. When an assistant reads the message to summarize or reply to it, it may follow those instructions instead of yours. The instructions are usually hidden using techniques like zero-size or white-on-white text, so the message looks completely normal to a person.
Can AI email summaries be wrong on purpose?
Yes. Forcepoint X-Labs demonstrated this on August 25, 2026: hidden instructions in an email caused a summarizer to report an invoice of 231,000 euros instead of the real 46,200 euros, and a due date of September 3 instead of the real August 21. It worked in all 10 test runs, and the hidden instructions never appeared in the summaries, so the reader had no way to know.
How is prompt injection different from phishing?
Phishing targets a person and works when someone clicks a link or replies. Prompt injection targets the AI model reading email on that person's behalf and works when the model follows an injected instruction. Phishing relies on urgency and deception the reader might notice. Prompt injection relies on text the reader cannot see at all.
Does Microsoft Defender stop prompt injection emails?
Microsoft Defender for Office 365 Plan 2 detects prompt injection content in inbound email before it reaches a mailbox or an AI assistant, with no extra configuration needed. It analyzes the message the way an assistant would receive it, including hidden text and encoded segments, and classifies detections under High confidence phishing with a detection technology value of "Prompt injection protection." Plan 1 and standard Exchange Online Protection do not include it.
Is Microsoft 365 Copilot safe to use for email summaries?
Copilot has its own protections at model runtime, including input filtering, separation of your instructions from message content, limits on what it can access, and output filtering. Those are real but they are one layer. Microsoft's own guidance frames mail-layer detection in Defender for Office 365 Plan 2 as a separate and earlier layer, on the reasoning that if one control is bypassed another still stands. Treat summaries as a convenience rather than a source of truth for anything involving money.
How can hidden text be invisible to me but readable by AI?
Your email client renders the message and shows you the result, discarding anything styled to be invisible. The AI assistant usually receives the raw source instead, where that text is still present and reads as ordinary content. The Forcepoint test used text styled with zero font size, zero line height, and white color, which Outlook displayed as nothing.
Can prompt injection make an AI assistant leak my data?
That is one of the documented risks. Microsoft lists leaking sensitive mailbox content, misclassifying a malicious message as safe, generating a misleading summary, and taking an unwanted action in an automated workflow as possible outcomes of a successful injection. The more permissions an assistant has, the more an injection can do with them.
What should I tell my staff about AI email summaries?
One sentence covers most of it: the summary is a convenience, not a source of truth, and anything involving money, a deadline, or bank details gets checked against the actual email and verified by phone on a number you already had. This is worth saying explicitly, because normal phishing training teaches people to spot something that looks wrong, and this attack is designed to look completely normal.
Does this affect Gmail and other email providers too?
The technique is not specific to Outlook or Microsoft. Any AI assistant that reads raw message content it did not author is exposed to the same problem, which is why the researchers' recommendation is aimed at how tools are built rather than at one product. What differs by provider is what filtering sits in front of the mailbox, so the practical question for your business is which protections your specific plan actually includes.
Is this a real attack or just a lab test?
The invoice test was a controlled proof of concept. The broader technique is not theoretical: Forcepoint X-Labs separately documented indirect prompt injection payloads found in the wild, and Microsoft shipped detection for prompt injection in inbound mail as a production feature in August 2026. Vendors do not usually build filtering for problems nobody is having.
What is the single most useful thing to do first?
Check which Defender for Office 365 plan your business actually has. It is a five-minute answer, it decides whether you have mail-layer protection at all, and most owners are surprised by what their license really includes.

Who at Your Company Would Catch It?

If an invoice email arrived tomorrow with the wrong number hidden inside it, who would notice? Two questions worth answering this week: which Defender plan are you actually licensed for, and how many tools currently read your email. Most owners are wrong about at least one. We handle both as your outside IT and security team — and we will start by telling you what your license actually covers.

  • Your actual Defender license tier
  • Every tool reading your mailbox
  • The one money rule your staff needs
30 Minutes · No Pressure · No Obligation