// reference investigation

reed-smart-home-compromise — multi-vendor IoT intrusion cluster

Jordan Reed's smart home abused while traveling: Alexa unlock commands, Google Home guest lock add, HomeKit geofence plist, Ring motion + live view, Nest unfamiliar face, August guest code at 03:22 UTC, thermostat away override, rogue Samsung TV account. Fully synthetic.

what this proves

  • all eight smart-home-compromise primary engines produce deterministic, fixture-locked output — verified by npm run check:flagship (280/280 fleet · 8 for this scenario).
  • every output is generated 100% locally in your browser — vendor exports never upload.
  • alexa unlock commands, google home guest lock add, ring live view while away, august guest code at 03:22 utc, thermostat away override, and rogue samsung tv account surface without sending evidence to a server.

primary engines locked to this fixture

build the case binder

runs all eight primary engines on the synthetic evidence zip and opens a self-contained html binder. uses the default binder renderer for smart home — no upload.

runs all 8 primary engines locally on the synthetic evidence zip · opens a self-contained html binder · no upload

download the synthetic evidence

MIT-licensed, fully synthetic. includes alexa voice history csv, google home activity json, homekit accessory plist, ring events json, nest camera export, smart lock access csv, thermostat timeline json, samsung tv viewing json, and case summary.

built deterministically from scripts/fixtures/build-reed-smart-home-compromise.mjs. seed: reed-smart-home-compromise:v1.

methodology

smart home compromise is multi-vendor correlation — walk alexa voice history → google home → homekit plist → ring → nest → lock csv → thermostat → tv last. guest-code slot name and unlock timestamp are your attribution anchor. read the full smart home compromise guide →

after the playbook

run each primary locally — or export findings from the binder — then drop every csv/json into fatcousin-multi-tool-super-timeline-correlator. one timestamp-sorted timeline across alexa unlock, google home guest lock add, ring live view, guest code at 03:22 utc, and thermostat away override — still zero upload.

synthetic scenario only · no real household · no real victim · grading rubric

ready