Is VIPRE URL Filtering safe?

Clean risk

VIPRE URL Filtering sends HTTPS page URLs and headers to its local native security host.

The extension watches main-frame HTTPS requests, caches their request or response headers, and sends the URL, HTTP method, browser name, and headers to com.vipre.https_url_filter for filtering. If the native host enables payload scanning, it refetches GET pages without credentials and sends the response bytes or hex string plus size to the same local host.

Vipre Securityv2.0.26Chrome Web Store
0Risk
Who publishes it

Vipre - no other listings under this identity

What this publisher told the store about itself, and the other listings that told it the same thing.

Publisher
Vipre Security
Declared legal entity
Vipre
Registered address
114 5th Ave, New York, NY 10011, US
Registered contact
Vipre Security

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 2.0.26. 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 every secure site you visit

    https://*/*

  • See the address and title of every tab you have open

    tabs

  • Talk to a program installed on your computer, outside the browser's sandbox

    nativeMessaging

  • Store data in your browser

    storage

  • Watch every request your browser makes

    webRequest

Where it sends data

Destinations our analysis observed Chrome Release Filter 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.

  • com.vipre.https_url_filter

    Chrome Release Filter sends data to com.vipre.https_url_filter. No other extension we have analysed sends data here.

Updated 30 September 2026hojbhchonecljnbcinbdfhkahanhogbm