Is Chrome Unlock New Bing AI safe?
Chrome Unlock New Bing AI rewrites browser identity headers on Bing requests to make Chrome look like Microsoft Edge.
When you open Bing pages or WebSocket connections, its declarativeNetRequest rule changes the User-Agent and sec-ch-ua client-hint headers before the request is sent. The modified headers describe Microsoft Edge/Chromium values and are sent only to Bing-matching URLs.
Who publishes it我是小马甲~~ - 1 other listing from the same operator, none carrying a finding
我是小马甲~~ - 1 other listing from the same operator, none carrying a finding
What this publisher told the store about itself, and the other listings that told it the same thing.
Same store account
1 other listing published from this account, 2k+ users between them, none of them carrying a finding.
Shared hosts - 1 hostname
Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
What it can do
Permissions this extension asks for, as declared in version 1.0.4. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Read and change your data on bing.com
*://*.bing.com/*
Block and redirect the requests your browser makes
declarativeNetRequest
Where it sends data
Destinations our analysis observed Chrome Unlock New Bing AI contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.
- *.bing.com
Chrome Unlock New Bing AI sends data to *.bing.com. One other extension we have analysed sends data here.