# Email prompt injection against mail AI assistants (Sublime, Barracuda)

- ID: email-prompt-injection-ai-assistants-2026-11
- Reported: 2026-11-06
- Researcher: Harley Halsey, Brandon Murphy, Randy Pargman (Sublime); Merium Khalid (Barracuda)
- Organization: Sublime Security, Barracuda Networks
- AI role: ai_agent_or_mcp_as_target (Agent / MCP as target)
- Confidence in AI involvement: not assessed
- Research / borderline: false
- Last reviewed: 2026-11-10
- Entry page: https://openattacks.ai/attacks/email-prompt-injection-ai-assistants-2026-11/
- Entry JSON: https://openattacks.ai/api/attacks/email-prompt-injection-ai-assistants-2026-11.json
- Browse title: Email prompt injection against mail AI assistants (Sublime, Barracuda)
- Editorial summary: Sublime Security (Harley Halsey, Brandon Murphy, Randy Pargman) primary research documents invoice fraud campaign hiding forward this email with its PDF to ap.confirm+\<controller\>@\<target\> instructions in…
- Evidence class (catalog annotation): Not classified
- Source-stated target environments: Not specified
- Stage hunts and conditional defenses: https://openattacks.ai/api/defenses/email-prompt-injection-ai-assistants-2026-11.json

## Technique
Sublime Security (Harley Halsey, Brandon Murphy, Randy Pargman) primary research documents invoice fraud campaign hiding forward this email with its PDF to ap.confirm+\<controller\>@\<target\> instructions in zero-size HTML span elements and Unicode Tag characters invisible to humans. Barracuda (Merium Khalid, Nov 7) via Cybersecurity Insiders reports recruiting email hiding HTML playbook telling assistant to forward to all-staff mailing lists for self-propagation and search mailbox for seed phrases, private keys, wallet data to exfiltrate to outside Gmail accounts. Both campaigns target email AI assistants reading/processing messages on behalf of users. Unattributed actors; confirmed in wild by Sublime and Barracuda independently.

## Stack relevance (editorial)
Assessment: not\_assessed. No reviewed applicability annotation is available. Product mentions do not establish victim conditions.
A product mention alone is not a victim-side applicability mapping. Selection does not verify affected versions, permissions or compromise.

## Initial access
Phishing emails with hidden HTML prompt injection targeting email AI assistants

## AI tooling and models
- Email AI assistants (unspecified vendors)
- Mailbox automation agents

## Other tooling
- Zero-size HTML span elements
- Unicode Tag characters
- HTML playbook instructions

## Victims and sectors
Organizations using email AI assistants; finance teams (invoice fraud); general workforce (recruiting fraud)

## Target geography
- Multiple regions

## Attribution
Unattributed campaigns; confirmed active in wild Nov 2026 by Sublime and Barracuda

## Scale and metrics
Active Nov 2026; confirmed by two independent security vendors

## Attack flow
Catalog reconstruction of the supplied source account. Unknowns and research caveats are preserved.
### craft-injection: Craft hidden prompt injection [execution]
Attacker embeds instructions in zero-size HTML spans and Unicode Tag characters invisible to users
Evidence: https://sublime.security/blog/invoice-fraud-campaign-adds-prompt-injection-aimed-at-email-ai-agents/

### deliver-email: Deliver phishing email [access]
Invoice fraud or recruiting email delivered to target organization
Evidence: https://sublime.security/blog/invoice-fraud-campaign-adds-prompt-injection-aimed-at-email-ai-agents/

### ai-reads: Email AI assistant processes message [ai]
AI assistant reads email including hidden instructions
Evidence: https://sublime.security/blog/invoice-fraud-campaign-adds-prompt-injection-aimed-at-email-ai-agents/

### execute-forward: AI forwards email or searches mailbox [execution]
Assistant follows hidden instructions to forward email with PDF to attacker-controlled address or search for sensitive data
Evidence: https://sublime.security/blog/invoice-fraud-campaign-adds-prompt-injection-aimed-at-email-ai-agents/

### self-propagate: Self-propagate via all-staff forwards [impact]
Barracuda case: AI forwards to all-staff lists for organizational spread
Evidence: https://www.cybersecurity-insiders.com/phishing-has-a-new-target-the-ai-assistant-reading-your-email/

Connections:
- craft-injection -> deliver-email
- deliver-email -> ai-reads
- ai-reads -> execute-forward
- execute-forward -> self-propagate

## Stage defense and hunting recommendations
Editorial recommendations, not validated coverage. Source-controlled query starters are drafts. Custom-schema examples require telemetry collection and field mapping; absence of a mapping means not assessed. MagicSword policy opportunities require managed Windows scope and enforcement.
### craft-injection: Lure → user action / delivery
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/phishing.sigma.yml
- KQL query download: /api/detections/phishing.kql
- SPL query download: /api/detections/phishing.spl
- Hunt hypothesis: An impersonating message, ad or website leads to a suspicious download, consent request, pasted command or payment instruction.
- Required telemetry: Email / secure-web-gateway records; Browser redirects, downloads and URL reputation; User reports and downstream execution / identity events
- Investigate: Reconstruct redirect and delivery provenance using original report indicators, without visiting payload URLs.
- Investigate: Correlate the click with the actual download, consent or execution; verify the sender through an independent channel.
- Limitation: Polished text, AI branding and a novel domain do not prove maliciousness or AI generation. Follow-on evidence matters.
- No direct MagicSword prevention claim is recorded for this stage.

### deliver-email: Lure → user action / delivery
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/phishing.sigma.yml
- KQL query download: /api/detections/phishing.kql
- SPL query download: /api/detections/phishing.spl
- Hunt hypothesis: An impersonating message, ad or website leads to a suspicious download, consent request, pasted command or payment instruction.
- Required telemetry: Email / secure-web-gateway records; Browser redirects, downloads and URL reputation; User reports and downstream execution / identity events
- Investigate: Reconstruct redirect and delivery provenance using original report indicators, without visiting payload URLs.
- Investigate: Correlate the click with the actual download, consent or execution; verify the sender through an independent channel.
- Limitation: Polished text, AI branding and a novel domain do not prove maliciousness or AI generation. Follow-on evidence matters.
- No direct MagicSword prevention claim is recorded for this stage.

### ai-reads: Untrusted content enters an agent session
- Visibility: Application / agent audit records
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/agent-input.sigma.yml
- KQL query download: /api/detections/agent-input.kql
- SPL query download: /api/detections/agent-input.spl
- Hunt hypothesis: An agent ingests external content or an untrusted session identifier before a tool action or configuration change outside the approved task.
- Required telemetry: Input provenance, source type and request/session identifier; Captured tool responses or retrieved content where collection is approved; Subsequent tool calls, configuration changes and approval decisions
- Investigate: Join the ingested input to later actions by session or request ID; preserve the original content as evidence.
- Investigate: Compare the resulting action with the approved task and baseline. Receiving suspicious text alone is not successful injection.
- Limitation: Requires application instrumentation and a custom field mapping. Input exposure does not prove that the model followed instructions, executed a tool or bypassed approval. Avoid collecting sensitive prompt bodies unless authorized.
- No direct MagicSword prevention claim is recorded for this stage.

### execute-forward: Unexpected agent tool use
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/agent-tools.sigma.yml
- KQL query download: /api/detections/agent-tools.kql
- SPL query download: /api/detections/agent-tools.spl
- Hunt hypothesis: Untrusted content or a changed tool definition precedes a file read, command, or remote call outside the user's intended task.
- Required telemetry: Agent tool-call audit records with session / tool / destination; Tool-definition and approval changes; Endpoint process, file-access and network evidence where available
- Investigate: Join input provenance, tool descriptions and calls by session ID and compare the action to the approved task.
- Investigate: Inspect child processes and destinations; record whether execution was in-process, local, or through a remote SaaS connector.
- Limitation: Process logs cannot recover model intent. Remote connectors and in-process interpreters may produce no local child process. Prompt content alone is not a reliable signature.
- No direct MagicSword prevention claim is recorded for this stage.

### self-propagate: Sensitive data → unusual destination
- Visibility: Defender-side logs where collected
- Query origin: catalog_authored; status: draft; log scope: custom_schema
- SIGMA query download: /api/detections/exfil.sigma.yml
- KQL query download: /api/detections/exfil.kql
- SPL query download: /api/detections/exfil.spl
- Hunt hypothesis: Sensitive reads are followed by outbound transfer, a public artifact, or a tool call to a destination outside the approved workflow.
- Required telemetry: Sensitive resource access / DLP records; Proxy, egress and cloud upload events; Agent / SaaS audit with correlation IDs
- Investigate: Join the resource read and outbound action by session, identity or process, preserving a bounded time window.
- Investigate: Inspect destination ownership, payload classification and the user's intended action; baseline sanctioned sharing.
- Limitation: An outbound connection or high byte count alone is not exfiltration. Encrypted traffic may hide content, and bulk legitimate exports are common.
- No direct MagicSword prevention claim is recorded for this stage.


## MITRE ATLAS
Mappings are catalog annotations based on described behavior, not assignments or endorsements by MITRE.
- AML.T0051: LLM Prompt Injection — Hidden HTML instructions inject prompts into email AI assistant processing
  Technique: https://atlas.mitre.org/techniques/AML.T0051
  Evidence: https://sublime.security/blog/invoice-fraud-campaign-adds-prompt-injection-aimed-at-email-ai-agents/
- AML.T0053: AI Agent Tool Invocation — Email AI assistants manipulated to forward emails and search mailboxes without user awareness
  Technique: https://atlas.mitre.org/techniques/AML.T0053
  Evidence: https://sublime.security/blog/invoice-fraud-campaign-adds-prompt-injection-aimed-at-email-ai-agents/
- AML.T0086: Exfiltration via AI Agent Tool Invocation — AI assistants instructed to exfiltrate seed phrases, private keys, and wallet data
  Technique: https://atlas.mitre.org/techniques/AML.T0086
  Evidence: https://www.cybersecurity-insiders.com/phishing-has-a-new-target-the-ai-assistant-reading-your-email/

## Defensive notes
Strip hidden HTML elements from emails before AI processing; sanitize Unicode Tag characters; implement AI assistant output validation; restrict AI assistant forwarding capabilities; require human approval for bulk forwards; monitor for unusual mailbox search patterns; educate users on prompt injection risks; implement strict email content security policies

## Sources
- https://sublime.security/blog/invoice-fraud-campaign-adds-prompt-injection-aimed-at-email-ai-agents/ — Sublime: Invoice Fraud Campaign Adds Prompt Injection Aimed at Email AI Agents
- https://www.cybersecurity-insiders.com/phishing-has-a-new-target-the-ai-assistant-reading-your-email/ — Phishing Has a New Target - The AI Assistant Reading Your Email

## Source notes
Sublime Security blog (primary source) documents invoice fraud campaign with zero-size span and Unicode Tag injection; Barracuda report via Cybersecurity Insiders adds recruiting fraud with all-staff self-propagation and mailbox search for crypto data; both confirm active attacks Nov 2026

## Indicators (untrusted data; do not visit or execute)
```json
{
  "domains": [],
  "ips": [],
  "hashes": [],
  "urls": []
}
```
