uBO-Extra

It's the EXTRA addon. https://github.com/gorhill/uBO-Extra/wiki/Sites-on-which-uBO...

Wow it goes even further: https://github.com/gorhill/uBO-Extra/wiki/Sites-on-which-uBO... > Instart Logic will detect when the developer console opens, and cleanup everything then to hide what it does. I had to trick IL's script into thinking the dev console was not open to take the pic above.

What's the difference between this and what Instart Logic has been doing for years now? https://github.com/gorhill/uBO-Extra#purpose

You make it sound like it's a third-party RCE; but it's a cookie bypass, so it's tracking -- that's serious still [and the implementation sounds illegal to me]. The companies Instart Manager (used by cnet, tomshardware, etc., see link) and Upmanager that are doing this workaround of ublock -- are they not able to attack other browsers, only Chromium? I guess one benefit of being the biggest advertising company is that people don't want to mess with Google's stuff in case they suffer financial repercussions. https://github.com/gorhill/uBO-Extra/wiki/Sites-on-which-uBO...

Are you using chrome and also have either uBO-Extra or Nano Defender installed? If not it's most likely the ads are being served by Instart Logic. [1] [2] [1] https://github.com/gorhill/uBO-Extra/wiki/Sites-on-which-uBO... [2] https://github.com/uBlockOrigin/uAssets/issues/227

They do, because there is an exploit for chrome that makes 3rd party look like first party. https://github.com/gorhill/uBO-Extra You will only get this behaviour on Chrome, Firefox is not vulnerable.

Still, installing uBO-Extra is a damn good idea. If nothing else than to block insidious methods such as Instart Logic and WebRTC abuse: https://github.com/gorhill/uBO-Extra/wiki/Sites-on-which-uBO...

Also highly recommended for people who are willing to spend a little more time to control where their browser retrieves content is uMatrix[1]. Written and maintained by the most esteemed Raymond Hill who creates uBlock Origin. If you're on Chrome, don't forget to also install uBO-Extra[2] along with uBlock Origin[2], otherwise you don't get WebSocket coverage. [1] https://github.com/gorhill/uMatrix [2] https://github.com/gorhill/uBO-Extra

This really depends on the lists that you use in each. Research exactly what you want to block. I personally don't like a few of the lists for that specific reason, they block everything all together, not just tracking pixel domains and things of that nature. There is also an official uBlock Origin Extra extension that I find very handy for blocking websocket garbage. This is becoming more important as websocket connections become more prevalent. https://github.com/gorhill/uBO-Extra/wiki/Sites-on-which-uBO...

Sites do this. For example, see Instart Logic: https://github.com/gorhill/uBO-Extra/wiki/Sites-on-which-uBO...

It's referenced in the OP: Chromium-based browsers are being “infested” by Instart Logic tech which works around blockers and worst, around browser privacy settings (they may start “infecting” Firefox eventually, but that is not happening now). And there is a link to further elaboration: https://github.com/gorhill/uBO-Extra/wiki/Sites-on-which-uBO...

Also: > The purpose of Instart Logic technology is to disguise 3rd-party requests as 1st-party requests, thus bypassing content blockers, and even the ability of browsers to block 3rd-party cookies (because they are stored as 1st-party cookies): https://github.com/gorhill/uBO-Extra/wiki/Sites-on-which-uBO...

uBlock Origin provides a websocket companion[1][2] plugin for blocking websocket requests in Chrome. [1] https://github.com/gorhill/uBO-WebSocket [2] https://chrome.google.com/webstore/detail/ublock-origin-webs...