Discussions

Ask a Question
Back to all

Control D strategy against Bright Data / proxy SDKs on Smart TVs

Hi everyone,

I recently read an article about Residential Proxy networks (Bright Data, Oxylabs, etc.) being embedded in apps, Smart TVs and other consumer devices. The concern is that devices inside a home network could become part of a proxy/scraping network without the user being fully aware of it.

What is the recommended way to detect or block this with Control D?

Specifically:

  • Are there existing blocklists that cover Residential Proxy providers such as Bright Data, Oxylabs, NetNut, SOAX and similar services?
  • Can Control D identify devices making connections to these networks?
  • Is there a recommended policy setup to prevent Smart TVs, Android TV devices and mobile apps from participating in proxy networks?
  • Has anyone built custom filters for this use case?

I’d be interested in hearing how other users approach this problem.

Thanks!