Google Home speakers secretly consume hundreds of gigabytes of Wi-Fi data due to mDNS flooding bug
A severe server misconfiguration causes smart audio devices to blast continuous multicast discovery storms, triggering ISP bandwidth caps and Wi-Fi congestion.
Technology news
A pervasive firmware and server configuration flaw affecting Google Home and Google Nest smart speakers has been causing devices to generate massive, uninterrupted streams of background network traffic, silently consuming hundreds of gigabytes of residential broadband data over short operating windows.
The anomaly was initially uncovered by home network administrators and smart home enthusiasts after receiving ISP notifications warning of impending monthly data-cap overages. Detailed router traffic inspections revealed that ostensibly idle Google smart speakers were continuously transmitting multicast DNS (mDNS) discovery packets and initiating recursive TCP handshake requests to cloud backends at rates reaching thousands of requests per hour, with some single households clocking between 400 GB and 3 TB of ghost usage in a fortnight.
In a formal statement to WIRED, a Google engineering spokesperson verified the flaw: 'A server misconfiguration caused certain Google Home and Nest speaker hardware revisions to enter repetitive connection handshake loops upon encountering intermittent local network timeouts. We have developed and deployed a server-side mitigation and are pushing an automated firmware patch to fully restore expected local network traffic behavior.'
Beyond the immediate financial sting of unexpected ISP data overage fees for affected consumers, network engineers caution that the bug exposed critical weaknesses in smart home local device discovery protocols. Continuous mDNS broadcast storms can saturate consumer router routing tables, degrade local Wi-Fi latency, and disrupt neighboring Internet of Things peripherals, underscoring the necessity for robust local device isolation on residential networks.