Updated for 2026
Most AI Extensions Are Never Audited
The Chrome Web Store hosts over 180,000 browser extensions. Many — mainly AI tools — ask for wide access. They read every page you visit. They see your clipboard. They can block or alter network requests.
USENIX Security 2025 found that 83% of Chrome extensions with broad permissions have never been audited. Developers built them, published them, and users installed them by the millions. No one checked whether each tool does only what it claims.
That gap is structural. The Chrome Web Store scans for known malware. It checks policy rules. It cannot confirm whether data collection is fully disclosed. It cannot detect whether data flows to hidden third parties.
Half of Enterprise Workers Run Unapproved Tools
LayerX's 2025 Enterprise Browser Security Report found that 45% of enterprise employees use browser extensions that IT never approved. The pattern is common. An employee finds a useful tool. They install it. IT never finds out.
Combine 83% unaudited with 45% unapproved. Nearly half of enterprise employees may be running tools whose security has never been checked. Those employees handle sensitive company data every day.
For regulated sectors, the risk is direct. An HR employee using an unvetted tool that reads clipboard content may have sent personal data to an unknown third party. A lawyer using an unvetted AI writing tool may have sent client data to an unknown party. See our legal compliance guidance for how these risks map to GDPR, HIPAA, and related frameworks.
What the 900K-User Incident Shows
A reported incident in early 2026 shows the failure mode. Malicious Chrome extensions exposed the AI chat logs of an estimated 900,000 users. Around 600,000 came from one tool. About 300,000 came from another. Both appeared to offer real AI features. Both were listed in the Chrome Web Store. Both had large user bases.
Data theft was complete within 30 minutes of install. By the time researchers found the tools, nearly a million users had already lost control of their AI chat history. That included any sensitive content they had typed.
Incogni's 2025 study found that 67% of AI Chrome extensions collect user data. Collection practices, disclosure, and data targets vary widely across that group. See our security and compliance overview for how browser-level controls compare to trusting each tool's own conduct.
An Enterprise Governance Framework
Blocking all browser extensions is not realistic. The cost is too high. The right response is a governance framework that limits exposure to vetted, approved tools — mainly for AI use.
Extension allowlisting. Define which extensions are allowed on enterprise devices. Require a security review before adding any new tool. Use Chrome Enterprise policy to block installs outside the approved list.
Stricter review for AI tools. Any extension that handles AI prompts gets extra scrutiny. Check network traffic to see where data goes. Review the full permission scope. Verify publisher identity.
Browser-layer controls. For approved AI tools, apply controls that intercept sensitive content before it reaches AI providers. This removes the need to trust each extension's own conduct.
The 83% unaudited rate is not a problem users can solve. Users cannot audit Chrome extensions themselves. Enterprise governance — approved lists, policy enforcement, and tech controls — is the reliable answer. See our FAQ and glossary of browser DLP terms for more.
anonym.legal's Chrome extension runs PII scanning locally in the browser. No chat content reaches anonym.legal servers during scanning. The modified, masked prompt is what gets sent to the AI service.
When This Approach Has Limits
Enterprise governance — approved lists, policy enforcement, and browser-layer controls — is the right answer to the unaudited-extension problem. But it has boundaries worth naming honestly.
Governance binds managed browsers, not the whole workforce. Approved lists and policy enforcement apply where the organization controls the browser through enterprise management. An employee on a personal laptop, a home browser profile, or a device outside MDM enrollment can install whatever they like. The 45% who already reach for unapproved extensions are most likely to be on exactly the unmanaged surfaces governance cannot see. The control reduces risk on corporate endpoints; it does not extend to every place work happens.
A browser-layer interceptor still depends on detection. Masking sensitive content before it reaches an AI provider only masks what the local scanner recognizes as sensitive. A novel identifier, an unusual format, or context the model misreads can pass through. Local-only processing protects confidentiality of the scanning step, but it does not raise recall to certainty — the prompt that leaves the browser may still contain something the scanner did not catch.
Approval is a point-in-time judgment. An extension vetted today can turn malicious after an ownership change or a pushed update, a pattern documented repeatedly in the Chrome ecosystem. An approved list reduces exposure to unvetted code; it does not continuously guarantee that approved code stays trustworthy. Governance needs ongoing re-review and update monitoring, not a one-time allow decision — which is also why an interception layer that does not trust any single extension's conduct is the more durable control.