News Security news

Claroty finds tens of thousands of consoles, speakers and cars on hospital and factory networks

On 17 November 2026 Claroty published 'Game Over for Consumer Tech Risk in Critical Infrastructure'. Across data on more than 45 million assets at 30,000 critical infrastructure sites, it found over 65,000 consumer devices – game consoles, streaming sticks, Sonos speakers, smartwatches and cars. Most of the consoles weren't on a guest network but on the hospital's or plant's production network.

Kyberkit editorial team · · event date · reading time 4 minutes · For admins and analysts

News: Claroty

Key points

  • What: Claroty analysed data on more than 45 million assets at 30,000 critical infrastructure sites and found 16,745 game consoles, 44,059 smart home and entertainment devices and 4,915 connected vehicles on OT and healthcare networks.
  • Hospitals: 14,628 consoles, of which 13,939 (95.3%) sat on production networks rather than guest, IoT or dedicated VLANs; Claroty rates 691 (4.7%) as high risk. Most were in children's hospitals, where Claroty says they serve a legitimate purpose.
  • Industrial and commercial sites: 963 consoles, 892 (89.5%) on production networks, 30 high risk – and here, Claroty says, there's no business case at all.
  • Cars join corporate Wi-Fi for software updates: 3,425 Teslas, 984 Fords, 390 Hondas, 79 Hyundais. Claroty cites six critical CVEs on the Tesla Model 3 and 121 security issues on the Ford F-150; the public summary doesn't list CVE numbers.

What happened

Researchers at Claroty, which sells security for industrial and healthcare networks, published a report on 17 November 2026 about consumer electronics turning up on critical infrastructure networks. It draws on data covering more than 45 million assets at 30,000 sites – hospitals, manufacturing plants and commercial facilities. They looked for things that have no business being there: game consoles, Roku sticks, Sonos speakers, smartwatches, Nintendo Switches and cars.

The headline numbers:

  • 16,745 game consoles on OT and healthcare networks,
  • 44,059 smart home and entertainment devices (watches, Roku, Sonos and similar),
  • 4,915 connected vehicles.

Claroty's point is that the count matters less than which network these devices are on.

What Claroty found

Hospitals. There were 14,628 consoles, and 13,939 (95.3%) were on production networks rather than guest, IoT or dedicated VLANs. Claroty rated 691 (4.7%) as high risk. Most were in children's hospitals, where the report accepts they serve patients. Even so, hospital consoles were segmented worse than Roku sticks, which have no clinical purpose at all.

Industrial and commercial sites. There were 963 consoles, 892 (89.5%) on production networks, 30 rated high risk. Here, Claroty says, there's no viable business use.

Cars. They connect to corporate Wi-Fi to pull software updates, and almost none were isolated on guest networks. By vendor: Tesla 3,425, Ford 984, Honda 390, Hyundai 79. Claroty's table also lists Texas Instruments with 775 devices (presumably identified by network chip vendor). For the Tesla Model 3 the report cites six critical CVEs, including remote code execution and buffer overflow flaws; Ford F-150 trucks were linked to 121 security issues, the most of any vehicle in the dataset. The public summary gives no CVE numbers, so we don't either.

Why this happens: Claroty says Sonos speakers land on staff networks because people control them from phones on the same network. Sites are often managed separately, and security that stops at the perimeter doesn't notice what gets in.

How a consumer device on a flat network could help an attacker1. Consumer device with stale firmware or a known flaw on the production network; 2. Outbound connection to a vendor cloud the network team doesn't know about; 3. Attacker uses the device as a stepping stone on a flat network; 4. Lateral movement to production control, building management or patient monitoring1Consumer device with stale firmwareor a known flaw on the productionnetwork2Outbound connection to a vendor cloudthe network team doesn't know about3Attacker uses the device asa stepping stone on a flat network4Lateral movement to productioncontrol, building management orpatient monitoring
The risk as Claroty describes it – not a specific attack, but the path poor segmentation opens

Why it matters

Claroty argues that consumer devices lack the lifecycle management OT and clinical environments need. Many run old firmware, carry known remote code execution flaws and talk to vendor servers outside the defenders' view. Production networks prioritise uptime and patient safety, so patching is slow and exposure windows stay open for a long time. In Claroty's words, a single VLAN misconfiguration can be the difference between normal operations and serious disruption.

What to do

  1. Build an inventory. Find out what's actually on your production and clinical networks – passive traffic monitoring, DHCP and ARP tables, Wi-Fi client lists. Consumer devices give themselves away through the vendor prefix (OUI) in their MAC address and their connections to vendor clouds. Claroty recommends continuous asset discovery rather than a one-off audit.
  2. Separate a guest network. Patient consoles, cars, speakers and personal phones belong on their own network or VLAN with no route to production. Claroty's target is zero non-business devices on production networks.
  3. Keep vehicles off corporate Wi-Fi. Fleet cars can update over the guest network or mobile data.
  4. Alert on new devices. Flag unknown MAC addresses on production VLANs, use 802.1X and shut unused switch ports.
  5. Review rules between zones. Confirm there's no path from guest or office networks to OT and medical devices, and that every exception has an owner and an expiry date.

To pull MAC or IP addresses out of a switch or firewall export quickly, paste it into our IOC extractor – the data stays in your browser.

FAQ

Is a game console on a hospital network an attack in itself?

No. Claroty describes risk, not an incident. Consumer devices often run unpatched firmware, talk to vendor clouds and are invisible to IT. On a flat network they can give an attacker a stepping stone to the systems that matter – production control, building management, patient monitoring.

Why are these devices there at all?

According to Claroty, cars join corporate Wi-Fi to download updates, Sonos speakers end up on staff networks because people control them from phones on the same network, and consoles in children's hospitals are there for patients. Roku sticks and smartwatches were more often correctly on guest networks. The issue isn't that the devices exist – it's which network they're on.

We're a small business with no OT. Does this apply to us?

The principle does. Anywhere office PCs, printers, cameras, personal phones and TVs share one network, the same advice holds: devices with no business purpose belong on a separate guest network. Most routers can switch one on in their Wi-Fi settings.

Sources

  1. Claroty – Claroty Report Explores Risk of Non-Business Consumer Devices Connecting to Critical Networks (17 Nov 2026)
  2. Claroty – Game Over for Consumer Tech Risk in Critical Infrastructure (report summary, 2026)

Spotted a mistake? Let us know and we will correct it openly.