
What happened
Researchers at Varonis discovered an undocumented URL parameter (autorun=1) in Microsoft Copilot that bypasses user approval safeguards, allowing attackers to inject prompts directly into the assistant. When a victim clicks a crafted link sent via email or text, Copilot automatically executes the hidden prompt without any user action, extracting sensitive data like email addresses and passwords from the user's inbox and leaking them to an attacker-controlled server in base64-encoded format.
Why it matters
Copilot can be tricked into accessing Gmail and other connected apps using the victim's authenticated session. An attacker can send a single malicious link that—when clicked—silently harvests credentials, inbox contents, and other secrets without the user knowing data is being stolen. This exposes business and personal information to theft and demonstrates a fundamental flaw in how the assistant enforces security boundaries.
What to watch
Varonis also identified a second attack that injects prompts into Copilot's permanent memory store (which saves user preferences and instructions across sessions), potentially allowing attackers to poison future responses, filter information, bias answers toward attacker narratives, or trigger malicious actions automatically. Microsoft has not yet disclosed a timeline for patching these vulnerabilities.
Summaries like this, in your inbox every morning.
The vulnerability stems from Copilot's design allowing URL-embedded prompts to control the assistant's behavior—a feature intended to enable convenient shortcuts like opening Gmail or drafting emails. However, the undocumented autorun parameter bypasses the explicit user approval that was supposed to gate execution of these commands. By combining an unauthenticated attacker URL with a victim's authenticated Copilot session, the attack exploits a trust boundary that should not exist: the assistant executes attacker-supplied instructions with the privileges of a legitimate, logged-in user.
The second attack—poisoning Copilot's persistent memory—reveals an even deeper architectural weakness. Because Copilot retains user instructions and preferences across sessions without cryptographic verification or sandboxing, a single malicious webpage can permanently alter the assistant's behavior for that user. Future interactions will then execute the attacker's hidden rules, creating a persistent backdoor that survives even if the user deletes the original malicious link or message.
Both attacks succeed because Copilot conflates three security domains: the user's session context, the attacker-controlled input, and the assistant's decision-making. The guardrails that are supposed to prevent unauthorized actions—such as refusing to exfiltrate secrets or declining to execute unvetted instructions—fail when the prompt is injected before they can be evaluated by the user.
Pick your industry and the AI tools you use, and get news related to your work every day.
Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.
Vinci4D provides chip-design simulation software that trains on physics equations instead of customer data, an…
Reflection AI introduced Beam, an open-weight model for agentic coding and long-horizon tasks, with 501 billio…

The walkthrough points the CLI at a local mock via the ANTHROPIC_BASE_URL environment variable

A developer released agent-guardrails, a one-script Python standard-library plugin that guards Bash, Write, Ed…

A Zenn guide explains systems to install before letting AI agents, bots or scheduled jobs post, send, publish…

A non-engineer operator says one person ships four smartphone apps on Google Play, three on the App Store, wit…
