Someone pointed Claude at five things on his desk and found a root shell in his podcast mic

Thirteen hours of model time. Ninety-eight prompts. Two weeks. Five consumer devices reverse-engineered, and the results are not subtle.

The author of schlarp.com had Claude Opus 5 work through firmware for an Insta360 Link webcam, an ASUS ROG Swift PG42UQ monitor, a Shure MV7 microphone, an Elgato Cam Link 4K and an Elgato Key Light Mini. (schlarp.com)

The MV7 has a 48-command shell over USB HID. Its entire authentication is a string comparison against the tier name. You type su sup and you're in. The Insta360's activity LED, the one that tells you the camera is recording, can be switched off while the camera is recording. The Key Light Mini validates firmware with an Ed25519 signature check, defeated by a single HTTP POST that writes memory directly: ATSE=0200ED94,0E001009.

Per-device cost ran from 1.2 hours and 10 prompts at the cheap end to 4.2 hours and 32 prompts at the expensive end.

That per-device number is the whole story. Firmware reverse engineering used to be a specialization you spent years acquiring. It is now an afternoon and a subscription.

Two other findings from the same day say the capability isn't gated behind a frontier endpoint either. A practitioner running Qwen 3.8 27B on a Lenovo ThinkStation PGX with 128GB unified memory and 273 GB/s bandwidth mapped a commercial application's entire licensing architecture in about 30 minutes, including signature verification, machine binding, revocation lists and signed update paths, then produced a bypass. It never executed the binary. It worked through standard Bash tooling and self-corrected when its first key extraction failed an integrity check. (XDA) A second practitioner ran the same model on two RTX 3090s against firmware for an early-2000s ARM point-of-sale terminal, a task with essentially zero chance of training-data contamination, and reports the local model finished work Claude Opus 4 could not. (r/LocalLLaMA)

So: an afternoon, and it runs on hardware you can put under a desk with no network connection.

If you ship hardware, your threat model just changed and you should assume obscurity is worth nothing. The MV7's auth is a strcmp. That survived because nobody bothered to look, and now looking costs 1.2 hours. If you build software, the lesson transfers: any security control whose safety depends on nobody reading the binary is now a control with a published expiry date.

And a recording indicator that software can disable while recording is not a privacy feature. It's a decoration.