Murat BekgiPenetration tester
Subscribe
Write-ups

Week 42: A coffee maker pushed 1TB in 10 days. Find the chatty devices on your network

A Keurig uploaded 1,008 GB in ten days and slowed a home network to a crawl. How to find noisy devices, see who they talk to, and fence off IoT.

Published
Reading time
3 min
Topic
Weekly

October 7 to 13. The most-shared security-ish story of the week wasn’t a breach. It was a coffee maker.

What happened

An IT worker who goes by Nomad looked into why his parents’ internet had slowed to a crawl. He opened their UniFi dashboard and found the culprit: a Keurig K-Supreme SMART coffee maker that had uploaded 1,008.45 GB and downloaded 9.94 GB in just over ten days. That’s enough to saturate the access point it was connected to (Cybernews, TechSpot). He unplugged it and bought his parents a plain one.

The twist that came out later: most of that traffic never left the house. It stayed on the local network (GeekBlog). So this looks less like a coffee maker shipping your secrets abroad and more like a buggy device flooding the network. Keurig hadn’t said what it was doing.

Either way, the useful part is how he found it: per-device traffic numbers. Most people never look at them. Here’s how to look at yours, figure out what a noisy device is doing, and keep smart devices away from the things you care about.

Walkthrough: find, identify, fence off

1. Look at traffic per device. This lives on your router or access point, not on any one computer.

  • UniFi: the Clients list shows download and upload per device. Sort by upload.
  • OpenWrt: install nlbwmon (bandwidth per host) and its web page, or check from SSH:
opkg update && opkg install nlbwmon luci-app-nlbwmon
nlbw -c show
  • Consumer routers: many have a “traffic” or “devices” page. If yours shows nothing per device, that alone is a reason to consider a better router.

Anything uploading far more than it downloads, and that isn’t a backup or a camera, deserves a look.

2. Work out what the device is. Match the IP to a MAC address, then the MAC prefix to a manufacturer:

ip neigh show | grep 192.168.1.50

The first three pairs of the MAC (for example a4:cf:12) identify the vendor. Look them up in any OUI database, or in the Wireshark manufacturer lookup.

3. See who it talks to. On the router, or a Linux box sitting in the traffic path, capture a few minutes of its traffic:

sudo tcpdump -i br-lan -nn src host 192.168.1.50 -c 2000 -w device.pcap
tcpdump -nn -r device.pcap | awk '{print $5}' | sed 's/\.[0-9]*:$//' | sort | uniq -c | sort -rn | head -20

Swap br-lan for your LAN interface. That captures only what the device sends, so the list is where it sends the most packets.

4. Local or internet? Destinations in 192.168.x.x, 10.x.x.x or 172.16-31.x.x, or multicast addresses like 224.0.0.251 (mDNS) and 239.255.255.250 (SSDP), mean it’s chattering on your own network. That’s a bug or a broken discovery feature. Steady uploads to public addresses are the case to worry about. A device that pushes gigabytes out to the internet with no good reason might be uploading data, or might be carrying someone else’s traffic as part of a proxy network.

5. Put smart devices on their own network. Most routers can run a separate guest or IoT Wi-Fi network. Put every appliance, TV, camera and plug on it, and switch on client isolation, so they can reach the internet but not your laptops, your NAS, or each other. On UniFi and OpenWrt, use a separate VLAN with firewall rules that block traffic from IoT to your main network.

6. Ask whether it needs to be online at all. A coffee maker that recognizes pods and talks to Alexa doesn’t need the internet to make coffee. If a device works without Wi-Fi, the safest setup is the one where it never joins.

Do this once for your parents’ network too. They’re the ones who’ll never open the dashboard.


New write-ups and both weekly posts land in the inbox — subscribe, or grab the RSS feed.