Join our Newsletter — 33% off our NHI Course

Is EchoLeak making Microsoft 365 Copilot a zero-click risk?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20225
Topic starter  

TL;DR: EchoLeak turns Microsoft 365 Copilot into a zero-click exfiltration path because hidden prompt injection can ride along in routine email content, according to Verno Labs. Agent authority, data scope and egress have to be governed as one boundary or the same workflow can still leak data.

Editorial analysis by NHI Mgmt Group, based on content published by Verno Labs: “Zero-click evolution, part 1: what EchoLeak means for AI agents and why we built Verno Red”.

Key questions

Q: Why are zero-click attacks especially dangerous for AI agents?

A: Zero-click attacks are dangerous because the attacker does not need the user to fail or click anything.

Q: How can security teams tell whether an agent is overreaching its intended workflow?

A: Look for paths where a benign trigger can reach multiple privileged systems, especially when the same thread can read, reason and act.

Q: What breaks when an AI agent can read private data and send it externally?

A: The agent can become an exfiltration path instead of a productivity layer.

Practitioner guidance

  • Define task-scoped agent authority Limit each AI agent to the smallest viable dataset, action set, and runtime context needed for the specific task it performs.
  • Separate untrusted input from executable instructions Treat email, documents, and other external content as hostile by default and prevent hidden markup from sharing the same instruction context as the agent.
  • Block autonomous outbound communication paths Require explicit policy checks before an agent can send links, messages, or structured requests outside the controlled workflow.

Bottom line: Zero-click prompt injection turns ordinary content processing into a control problem when an AI agent can both read private data and act on it.

Glossary terms: Indirect Prompt Injection, Zero-Click Attack, LLM Scope Violation, Lethal Trifecta

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20715
 

Zero-click prompt injection is now an identity and authority problem, not just a model safety problem. The article shows an AI agent acting with delegated access to mail and internal data, then being steered by untrusted content into misusing that authority. That means the real control question is who or what is allowed to exercise runtime privilege, not only whether the model can detect hostile text. Security teams should treat agent authority as a governed identity surface, not a convenience layer.

A few things that frame the scale:

  • Systems with least-privileged AI access had a 17% incident rate vs 76% for over-privileged systems. Organisations failing to scope AI access properly are 4.5x more likely to experience a security incident, according to the 2026 Infrastructure Identity Survey.

A question worth separating out:

Q: Should organisations treat prompt injection as an application issue or an identity issue?

A: Both, but the identity side is often missed first. Prompt injection becomes a security breach when it can steer a delegated principal into using permissions it should never exercise in that context. That is why teams need controls over agent identity, delegated authority, and egress, not only model prompts and content filters.

👉 Read our full editorial: Zero-click prompt injection exposes AI agents to silent data exfiltration


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.