Data breaches → Pi-hole
Was your data in the Pi-hole breach?
2025 · pi-hole.net · ~29,926 accounts exposedLow severity · 3/10
Pi-hole (pi-hole.net) suffered a data breach in 2025 that exposed around 29,926 accounts. If you had an account, some of your personal data may be circulating in leaked databases. The fastest way to know is to check your own email — free, in about 30 seconds, no password required.
What happened
In July 2025, a vulnerability in the GiveWP WordPress plugin exposed the names and email addresses of approximately 30k donors to the Pi-hole network-wide ad blocking project. Pi-hole subsequently self-submitted the list of impacted donors to HIBP.
Breach details sourced from Have I Been Pwned, the industry-standard breach database. Risk analysis by Nullivo.
What was exposed, and why it matters
Not all breaches carry the same risk — what matters is which fields leaked. Here is what the Pi-hole breach exposed and what each item actually enables:
Links this leak to your other accounts — a reused username lets anyone build a profile of you across platforms.
Puts you on spam and phishing lists, and confirms to attackers that you hold an account with this service — which makes impersonation emails more believable.
What to do if you were affected
These steps are ordered for this specific breach — the most urgent action given what leaked comes first.
- Names and usernames: Search your usual username to see what else it exposes, and use distinct handles for sensitive accounts.
- Email addresses: Treat any message referencing this service with suspicion, and never act on links in unexpected emails.
- Check whether your own email appears in this breach — run a free scan to confirm before you spend time on the steps above.
How urgent is this now?
This breach is recent, so the data is actively traded and the risk is at its highest right now.
Remember: a breach can't be "un-leaked" — once a database is out, it exists in countless copies. The goal is to make the leaked data useless: change what can be changed, lock down what can't, and remove what has been republished.
Frequently asked questions
What data was exposed in the Pi-hole breach?
The Pi-hole breach exposed names and usernames, email addresses. Links this leak to your other accounts — a reused username lets anyone build a profile of you across platforms.
How many people were affected by the Pi-hole breach?
Around 29,926 accounts were exposed, making it a smaller, more targeted breach.
What should I do if I had a Pi-hole account?
Search your usual username to see what else it exposes, and use distinct handles for sensitive accounts. You can check whether your own email appears in this breach with a free Nullivo scan — no password required.
Breaches that exposed similar data
If the Pi-hole breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.
- Was your data in the Hello Cake breach? (2025, ~22,907 accounts)
- Was your data in the TehetségKapu breach? (2025, ~54,357 accounts)
- Was your data in the Frame & Optic breach? (2025, ~15,678 accounts)
- Was your data in the Eurofiber breach? (2025, ~10,003 accounts)
- Was your data in the CodeStepByStep breach? (2025, ~103,077 accounts)
- Was your data in the Chris Leong breach? (2024, ~27,096 accounts)