Browser extensions
Extensions run inside your visitors' pages but aren't part of your code. When the browser blocks or reports something an extension injected, there is nothing for you to fix, so this rule filters the report.
State: On
What it matches
CSP violations, integrity violations, COEP reports and deprecations whose script, style or request comes from an address that starts with one of these prefixes:
chrome-extension://(Chrome, Edge and other Chromium browsers)moz-extension://(Firefox)safari-web-extension://andsafari-extension://(Safari)ms-browser-extension://(legacy Edge) andmxaddon-pkg://(Maxthon)https://local.adguard.org/(AdGuard's user scripts)
For CSP, integrity and COEP reports the rule reads the blocked address (blockedURL); for a deprecation,
the script that called the deprecated feature (sourceFile). Only that one field counts: the page that
loaded the script, the rest of a stack trace and the user agent play no part. An inline script an extension adds
reports as inline, so the rule leaves it in your list.
Why it's noise
Password managers, ad blockers, translators and shopping helpers add scripts and styles to every page they run on, and
the visitor's browser reports each one. Under an enforcing policy the browser blocked the extension's script, style or
request. Under Content-Security-Policy-Report-Only it ran, and only the report was filtered. You can't
change the extension, and loosening your policy for it would weaken it for everyone.
What it can hide
Only reports that point at an extension address, and that includes a malicious extension skimming what visitors type
into your pages. Under an enforcing policy the browser blocked the skimmer's script or request. Under
Content-Security-Policy-Report-Only it ran, and the data may have left the page. Either way the report is
filtered: it never notifies, and you find it only under Show filtered, with the rule named.
Your CSP can't stop an extension the visitor installed: it can read the page and send data through requests your policy never sees. A filtered report, when one arrives, may be the only trace you get. Scripts your own pages load from your own or third-party hosts are never matched.
See the filtered reports
Pick Show filtered on the Issues or Reports list. Over MCP, pass
include_filtered: true; each report's noise_rule names browser-extension. See
Noise Rules.