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.
Editorial analysis by NHI Mgmt Group, based on content published by Expel: “On the radar: ChatGPT Stealer”.
Key questions
Q: What breaks when browser extensions can read AI chat content and tab URLs?
A: The browser session stops being a clean trust boundary.
Q: Why do malicious extensions create more than a privacy problem?
A: Because the captured content often includes corporate context, internal references, customer information, or even credentials pasted into chat.
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.
Practitioner guidance
- Block unapproved browser extensions Use browser management controls and policy enforcement to allow only extensions that have been reviewed, approved, and tied to a clear business need.
- Review extension permissions before approval Compare each extension's requested permissions with its advertised function and reject add-ons that ask for broad tab, page, or network access without justification.
- Prefer vendor-built AI clients and extensions Steer users toward official desktop apps, mobile apps, or extensions published directly by the AI provider so the browser add-on supply chain is narrower and easier to govern.
Bottom line: Malicious browser extensions can turn AI chat sessions into an exfiltration channel even when the AI service itself is well governed.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
19/08/2026 4:29 pm
Prompt poaching is a browser governance problem first and an AI privacy problem second. The extension is the control point, because it sits where users mix sanctioned and unsanctioned data flows inside the browser. If security teams focus only on the AI application, they miss the place where the capture actually occurs. Practitioners should treat extension approval, update control, and network egress as one governance surface.
A few things that frame the scale:
- 43% of security professionals are concerned about AI systems learning and reproducing sensitive information patterns from codebases, according to the State of Secrets in AppSec.
A question worth separating out:
Q: Should organizations block AI browser extensions or manage them more tightly?
A: Manage them tightly rather than banning AI tools outright. A blanket ban can push users to unsanctioned workarounds, but unmanaged extensions create covert collection paths. The better control is to approve specific add-ons, restrict permissions, inventory installs, and align browser policy with AI usage rules and data handling requirements.
👉 Read our full editorial: Prompt poaching in browser extensions exposes AI chats