this post was submitted on 05 Dec 2025
505 points (99.2% liked)

Technology

77096 readers
2763 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
505
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
129 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
[–] Cort@lemmy.world 1 points 1 day ago* (last edited 1 day 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