← All stories
● Covered by 1 source · 1 reportLow impact1 neutral

Home Assistant User Raises Privacy Concerns Over Secret Scanning Feature

🔄 Updated 22d ago
New to BrevFeed? We gather this story from every outlet covering it into one summary — ranked by real-world impact, not just the latest headline — so you never miss what matters. What is BrevFeed? →

Key points

  • User reported unauthorized secret scanning in Home Assistant.
  • Home Assistant states feature is old, hashes secrets locally.
  • Only first 5 characters of hash are sent to HIBP.
  • Feature can be disabled using `ha security options --pwned=false`.

Unauthorized Secret Scanning Reported

A Home Assistant user opened an issue on GitHub, expressing concern over an integration that appeared to be scanning their secrets without explicit authorization. The user stated they had not enabled any such plugins or integrations and viewed the activity as a significant privacy invasion, particularly the transmission of data, even if hashed, to external services.

Home Assistant's Response and Clarification

Home Assistant developers responded, clarifying that the secret scanning functionality is not new and has been part of the Supervisor for several years. They explained that the system checks application options marked as passwords, hashes them locally, and only sends the first five characters of the hash to the Have I Been Pwned (HIBP) service. This design was implemented with privacy as a core requirement, ensuring secrets do not leave the user's system.

Disabling the Feature

Initially, the user sought a way to disable the feature. Home Assistant confirmed that the check can be turned off using the command line: `ha security options --pwned=false`. The recent visibility of this feature was attributed to a fix in a warning mechanism, not a new deployment of the scanning itself.

User's Continued Concerns

Despite the explanation, the user, identifying as a security professional with experience in red teaming and password management deployments, reiterated their dissatisfaction. They argued that such a feature should be opt-in rather than enabled by default, citing potential abuse vectors for malicious actors.

✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →

The daily brief

One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.

One email a day. Unsubscribe in one click, any time.

Today's brief

Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.

~4 min · 3 stories · Nov 07

▶ Play today's brief Listen on Spotify

New every morning, and the back catalogue is archived by date.

Reporting from

A Home Assistant user reported an unauthorized integration scanning secrets and sending data to Have I Been Pwned (HIBP), raising privacy concerns. Home Assistant clarified that the feature has existed for years, hashes secrets locally, and sends only partial hashes, and can be disabled via a command line option.