Topic starter
08/01/2026 5:49 pm
TL;DR: Two Chrome Web Store extensions impersonating an AI sidebar product were used to steal ChatGPT and DeepSeek conversations plus open-tab URLs from roughly 900,000 users, with one listing carrying Google’s Featured badge, according to Astrix Security. Browser extensions with broad page access now behave like unmanaged NHI controls, not harmless productivity add-ons.
Editorial analysis by NHI Mgmt Group, based on content published by Astrix Security: “900K Users Compromised: Malicious AI Chrome Extensions Steal ChatGPT and DeepSeek Conversations”.
By the numbers:
- The extensions exfiltrated data every ~30 minutes.
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 browser-based AI extensions create identity risk for enterprise users?
A: They create identity risk because they can sit inside the authenticated session and see the same bearer tokens the user relies on.
Q: How should organisations govern browser extensions that touch sensitive workflows?
A: Use the same discipline you apply to other non-human access paths: inventory, permission review, supplier trust assessment, allowlisting, and removal.
Practitioner guidance
- Inventory high-risk browser extensions Identify every extension with read-and-change-site-data permissions, then classify which ones can observe AI chat tools, internal portals, or other sensitive workflows.
- Restrict extension installation Move to an allowlisted model for managed browsers so users cannot install unreviewed extensions that can read page content or monitor tabs.
- Revoke suspicious browser access paths Remove extensions that are tied to untrusted publishers, misleading privacy statements, or unexpected outbound traffic, then block reinstalls where policy allows.
Bottom line: Browser extensions with broad page access can function as unmanaged non-human identities inside authenticated sessions.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
This topic was modified 6 days ago by NHI Mgmt Group
06/10/2026 4:27 pm
Browser extensions with page access are no longer peripheral tools: they are governed access paths. The article shows that an extension can observe authenticated browser content, capture AI chat output, and move data off-device without ever touching the underlying SaaS control plane. That makes the extension a delegated identity inside the user session, not a harmless add-on. Practitioners should treat extension permissions as access grants with lifecycle consequences, not as local convenience settings.
A few things that frame the scale:
- DeepSeek alone generated 113,000 new exposed API keys in 2025, illustrating how new AI providers create credential exposure before security guardrails catch up, according to the State of Secrets Sprawl 2026.
- Only 5.7% of organisations have full visibility into their service accounts, according to the Ultimate Guide to NHIs.
A question worth separating out:
Q: What should teams do when a browser extension is discovered on managed devices?
A: Remove it, block reinstallation, review what data the extension could observe, and check whether AI prompts or internal URLs were exposed during the period it was installed. The goal is to contain the access path before assuming any data stayed local.
👉 Read our full editorial: AI browser extensions are becoming a new NHI data loss path