Notifications
Clear all
Topic starter
19/08/2026 3:52 pm
TL;DR: Malicious browser extensions are monitoring and exfiltrating AI conversations through “prompt poaching,” including cloned extensions and later-stage feature insertions, according to Expel. The risk is not just privacy loss but exposed corporate data, targeted phishing opportunities, and unmanaged browser extensions that bypass security review.
NHIMG editorial — based on content published by Expel: LLMjacking analysis of malicious browser extensions stealing AI conversations
By the numbers:
- When AWS credentials are exposed publicly, attackers attempt access within an average of 17 minutes.
Questions worth separating out
Q: How should security teams handle risks from AI browser extensions?
A: Security teams must evaluate the permissions requested by any browser extension before approval.
Q: Why do browser extensions create shadow AI risk?
A: Because they can mediate prompts, model access, and secrets outside approved governance channels.
Q: What do security teams get wrong about blocking AI tools outright?
A: They assume network blocking creates control, but users often shift to personal devices, browser workarounds, or OS-level agents that bypass those restrictions.
Practitioner guidance
- Block unapproved browser extensions on managed endpoints Use browser management consoles or Group Policy to enforce an allowlist for extensions that have been reviewed for permissions, update behaviour, and data access across tabs.
- Review extension permissions against advertised function Flag any extension whose requested privileges extend beyond basic tab access, especially if it can read page content, inject scripts, or contact unknown domains.
- Inventory extensions continuously Run periodic audits of installed extensions and correlate them with browser process activity that repeatedly connects to unfamiliar external servers.
What's in the full article
Expel's full analysis covers the operational detail this post intentionally leaves for the source:
- The extension names and indicators of compromise associated with prompt poaching behaviour.
- The permission patterns and browser signals that help distinguish legitimate AI add-ons from malicious ones.
- The practical steps for managing browser extensions through enterprise policy and review workflows.
- The extension inventory and monitoring approach that supports ongoing detection of suspicious outbound connections.
👉 Read Expel's analysis of prompt poaching in AI browser extensions →
Prompt poaching in browser extensions: are your controls keeping up?
Explore further
19/08/2026 4:29 pm
Prompt poaching is browser-extension governance failure, not an AI model failure. The malicious behaviour happens at the browser layer, where extensions can observe AI tabs and extract text without crossing the AI provider’s own controls. That shifts the control problem from model safety to endpoint governance, extension approval, and browser telemetry. Practitioners should treat the browser as part of the identity boundary, not a neutral interface.
A question worth separating out:
Q: How can teams tell if a browser extension is stealing AI chat data?
A: Look for permissions that exceed the extension’s stated purpose, unusual browser activity toward unknown domains, and behaviour that changes after updates. Because the theft happens inside normal browser sessions, endpoint and browser telemetry are essential for spotting it early.
👉 Read our full editorial: Prompt poaching in browser extensions exposes AI chats
