Use case P8 · Human
Car owner points Claude Code at a cheap aftermarket head unit and finds a call recorder and an app-reinstall script
- Privacy and security
- Advanced
- Claude Code
- Source checked · news article
The short version
What they did
The owner connected Claude Code to the inexpensive Chinese aftermarket head unit installed in his Honda Civic and had it inventory what was running. It is not Honda’s factory unit.
Result (as claimed)
The Drive reports the voice assistant “always used about a third of processing power, even while idle”, the preinstalled apps included “a call recorder (!)”, and there was “a script, set to reinstall QQMusic and Ximalaya”. The Drive calls it “bloatware—or spyware, if you’re being less charitable.”
Prompt
I’m inspecting my own aftermarket Android car head unit, [brand and model], connected over [USB or adb]. The car is parked. I want to understand what’s running before changing anything.
1. Make a read-only inventory of installed apps and running services, including processor use while idle.
2. Show permissions for microphone, location, contacts and network access, and look for startup tasks or scripts that reinstall apps.
3. Give me a table of app or service, observed behavior, permissions and what needs a closer look.Use plain words. Separate evidence of recording or tracking from suspicion based on a name or permission. Explain what you couldn’t inspect. Finish with proposed changes and how to undo each one, but wait for my approval before running any command that changes the unit.
Do it yourself
These steps are my suggested way in, not the owner’s setup.
What you need
- An Android-based head unit with developer options, and a USB cable or Wi-Fi connection.
- A computer with adb (Android’s free command-line tool) installed.
- A coding agent that runs in the terminal, such as Claude Code or Codex.
Start simple
- Ask a chat assistant how to turn on developer mode and USB debugging for your head unit model.
- Connect your computer to the head unit with the car parked and the engine off or in accessory mode.
- Start the coding agent and paste the Prompt above. Tell it to read only.
- Ask for a table of every app, what it does, and which permissions it has.
- Look up anything flagged before you act on it.
Take it further
- Ask it to find anything that runs at startup or reinstalls apps.
- Ask it to show which apps use the most processor time while idle.
- Disable one app at a time, with a written way to undo each change.
Check your work
- Look up each flagged app name yourself. Some are only system parts with odd names.
- Ask the agent to show the exact command before it runs anything that changes the unit.
- Safety: never do this while driving. Turn off the microphone and location permissions you don’t need, and know that a bad change can stop the unit from working.
Source checked. The link, author, date and quote were confirmed against the source. The result itself has not been reproduced. Prompt adapted for this library, inspired by the case. Business size: Individual. Results are quoted as the source claimed them and never improved. Spot an error or a broken link? Email charlie@cbarmorecpa.com.