Nearly half of LG’s Smart TV apps pack proxy SDKs from services like Bright Data, Massive, and Honeygain/Oxylabs. Bright Data’s code even lists local IP ranges (127.0.0.0/8, 10.0.0.0/8, 172.16.0.0/12, 169.254.0.0/16, 192.168.0.0/16, 255.255.255.255) to block, proving the TV can reach those addresses if policy allowed. In contrast, Massive and Honeygain/Oxylabs samples take a host:port from the server and open a raw TCP socket—with no private-range filters in the local versions we saw. That means a TV app can quietly turn your living room device into a node on a residential proxy farm. Screensavers, novelty games or clocks can tap your home’s bandwidth. None of the apps we reviewed prompt you again after installation or explain how much traffic will flow through your network, what locations your IP will appear in, or how third parties might use that connection. Consumers assume a TV is just a display. They don’t expect it to run hidden network services. Worse, consent screens in TV apps are one-off, easy for anyone in the house—including kids—to click past without understanding. There’s no ongoing control panel, no per-app bandwidth meter, and no strong platform rules forcing clear disclosures. Platforms need to demand meaningful transparency and real controls before letting these SDKs into mass-market devices.