Why is my LG Washing Machine using 3.6GB of data/day?

Original Article ↗ Hacker News Discussion ↗

An internet-connected LG washing machine was found to be using around 3.6GB of data per day, prompting speculation about bugs, failed updates, data exfiltration, or even botnet activity and leading the owner to block its network access. Commenters explore how to investigate such traffic with tools like tcpdump and Wireshark, question the necessity and security of “smart” appliances that depend on cloud backends, and contrast the minor conveniences of connected features with long-term risks such as surveillance, insecurity, and forced obsolescence.

Suspected Causes of the Data Usage

  • Many think the behavior is abnormal; 3.6 GB/day is seen as unjustifiable for a washer.
  • Hypotheses include:
    • Part of a botnet or being used for data exfiltration.
    • A buggy loop repeatedly downloading or uploading firmware or updates.
    • A misdesigned notification/telemetry loop sending excessive data.
  • The high upload relative to download makes exfiltration or repeated status reporting seem plausible to some, but nothing is confirmed.

What the Owner Observed & Immediate Mitigation

  • The owner blocked the machine’s internet access and moved it to a segregated Wi‑Fi network.
  • Router logs later showed it contacting an LG ThinQ domain, which others note is an official LG endpoint.
  • After isolation, upload traffic appeared to stop, but prior traffic logs are missing, so the root cause remains unclear.

Suggestions for Investigation

  • Put the washer on its own VLAN/SSID and capture traffic with tcpdump/Wireshark.
  • Examine DNS queries and connection targets; correlate with router/firewall logs.
  • Some propose MITM/HTTPS inspection if certificate pinning is absent; others note that at least the Android app uses pinning.
  • OpenWrt/Asus + Entware setups are suggested as practical ways to pcap traffic at home.

Debate: Why Are Appliances Online at All?

  • Critics:
    • See this as unnecessary risk and data harvesting; call IoT appliances “actively malicious” or long‑term scams.
    • Worry about botnets, backend shutdowns causing e‑waste, and opaque telemetry.
  • Supporters (cautious):
    • Value notifications when cycles finish, low‑energy scheduling, maintenance reminders, and integration with home automation.
    • Would prefer local APIs/MQTT and LAN-only control, not opaque cloud connections.

Workarounds and Alternatives

  • Many isolate “smart” devices on guest networks/VLANs, often with DNS filtering (e.g., AdGuard Home).
  • Others refuse to connect appliances at all, or block them at the router/MAC level.
  • DIY solutions: smart plugs measuring power, accelerometers, or relays on start buttons combined with home-automation rules to detect cycle completion.

Broader Concerns

  • Discussion broadens to “downloadable cycles” as trivial but data‑hungry features.
  • People question cost/benefit, firmware quality, and safety/regulatory limits on remote control (e.g., ovens, breakers).