Page 1 of 1

Calls on first install of a browser

Posted: Thu Aug 29, 2019 1:40 am
by MikeGale
This is pretty specialised at the moment, but could conceivably become mainstream.

When a browser is first installed it typically goes out and makes a lot of calls, some to pretty odd places. If the general populace caught wind of what is going on it might change their browser habits.

Some of those calls, it turns out, are pretty surprising. Browsers that claim to be secure making obvious calls to surveillance / advertising sites. That presumably automatically infects machines with personally identifiable GUID's before the user even starts using it, may even be de-anonymised in advance.

I'm interested to see that a developer in the Brave browser team, is documenting this behaviour using the Fiddler debugging proxy.

He is getting some traction (on Twitter) with his work.

If anybody is interested, his ID on Twitter is @jonathansampson .

(I've caught browsers making automatic calls, that their support teams can't explain. Puts a new complexion on prosecuting people for using website X!)

Some of the write ups as Tweets:
  1. Safari ... 0794388481
  2. Opera ... 3308129281
  3. Vivaldi ... 5922059266
  4. Brave ... 1999518720
  5. Edge (Chromium version Beta) ... 2509065218
  6. Chrome ... 6441779200
  7. Firefox ... 6176660480
The beta Edge version shows that MSFT does not have the equivalent of Mr Sampson on their team. They currently are reported to call Google APIs, Google, Double Click, Google Ad Services, Facebook, Twitter Ads among others. Presumably from a page that is automatically invoked. Not a smart move.

Re: Calls on first install of a browser

Posted: Tue Nov 12, 2019 10:51 am
by Albert Wiersch
A little late to reply but I did look at this when you posted it. Very interesting.... a little surprising that there are so many calls but at the same time it's not that surprising.