this post was submitted on 05 Dec 2025
452 points (99.1% liked)

Technology

77096 readers
1709 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
L4s@hackingne.ws
452
Manufacturer issues remote kill command to disable smart vacuum after engineer blocks it from collecting data — user revives it with custom hardware and Python scripts to run offline (www.tomshardware.com)
submitted 1 day ago by spaghettiwestern@sh.itjust.works to c/technology@lemmy.world
114 comments fedilink hide all child comments
 

An engineer got curious about how his iLife A11 smart vacuum worked and monitored the network traffic coming from the device. That’s when he noticed it was constantly sending logs and telemetry data to the manufacturer — something he hadn't consented to. The user, Harishankar, decided to block the telemetry servers' IP addresses on his network, while keeping the firmware and OTA servers open. While his smart gadget worked for a while, it just refused to turn on soon after. After a lengthy investigation, he discovered that a remote kill command had been issued to his device.

you are viewing a single comment's thread
view the rest of the comments
[–] core@leminal.space 6 points 1 day ago (1 children)

Man itd be great if there was an answer to this. Maybe in an article somewhere. Guess we'll never know.

[–] sem@lemmy.blahaj.zone 2 points 23 hours ago (2 children)

Not to fear! Here is the relevant part so the next person coming by doesn't have to read the article:

deep in the logs of his non-functioning smart vacuum, he found a command with a timestamp that matched exactly the time the gadget stopped working. This was clearly a kill command, and after he reversed it and rebooted the appliance, it roared back to life.

a smart vacuum\'s components and sensors

(Image credit: Harishankar)

So, why did the A11 work at the service center but refuse to run in his home? The technicians would reset the firmware on the smart vacuum, thus removing the kill code, and then connect it to an open network, making it run normally. But once it connected again to the network that had its telemetry servers blocked, it was bricked remotely because it couldn’t communicate with the manufacturer’s servers. Since he blocked the appliance’s data collection capabilities, its maker decided to just kill it altogether. "Someone—or something—had remotely issued a kill command,” says Harishankar. “Whether it was intentional punishment or automated enforcement of 'compliance,' the result was the same: a consumer device had turned on its owner.”

[–] core@leminal.space 1 points 1 hour ago

( ͡° ͜ʖ ͡°)

[–] 0x0@lemmy.zip 0 points 23 hours ago (1 children)

it was bricked remotely because it couldn’t communicate with the manufacturer’s servers.

That bit seems inaccurate... if it couldn't communicate it wasn't bricked remotely... it was more like digital seppuku.

[–] sem@lemmy.blahaj.zone 1 points 21 hours ago (1 children)

Earlier in the article he says that he only disabled some of the network connections but he left open the ones for firmware updates and stuff so to me it's not impossible that it was able to receive remote commands although I would certainly want to see more technical details to satisfy my curiosity.

The article says in words that it was a remote command. But again, we don't have any details supporting that description. So maybe the journalist got it wrong.

[–] 0x0@lemmy.zip 0 points 21 hours ago (2 children)

I would certainly want to see more technical details

Certainly. By default most home networks block incoming traffic but then again if the's the tinkerer type his network will most likely not be default.

[–] sem@lemmy.blahaj.zone 1 points 17 hours ago

This is something I've never understood about firewalls. If the vacuum cleaner is uploading and downloading stuff from https://somecorpo.net/, what stops it from listening for remote commands on that same connwction?

[–] Cort@lemmy.world 1 points 17 hours ago* (last edited 17 hours ago)

Or the kill command could have been a response to a request made by the vacuum.

Vacuum #2566247: checking in for firmware updates

Server response: it's been 3 months since we received any telemetry data from vacuum #2566247 -- Execute Order 66