Chrome extension: what permissions usually make privacy leakage happen?

by TJCLARK   Last Updated October 18, 2018 09:03 AM

I am studying how privacy leakage happens by Chrome extensions.

First, "privacy leakage" I mean, for example, the extension sends host users browsing history/behaviors to 3rd party.

Second, I found the permissions are defined in "manifest.json" of extension source code.

My question is:

  1. What kinds of permissions are usually used by extensions to intentionally cause privacy leakage?

  2. I guess some permissions like "webRequest", "storage" may be relevant, right?

  3. What means "webRequestBlocking"? I checked but still not sure. Please use an example to explain. Just for example, "Flatbook" extension uses webRequestBlocking.

Related Questions

Youtube Playlist Autoloading

Updated November 26, 2015 06:01 AM

Why Google Hangout has two extensions for Google Chrome?

Updated September 11, 2016 09:01 AM