Data breaches → ZAP-Hosting
Was your data in the ZAP-Hosting breach?
2021 · zap-hosting.com · ~746,682 accounts exposedCritical severity · 9/10
ZAP-Hosting (zap-hosting.com) suffered a data breach in 2021 that exposed around 746,682 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 November 2021, web host ZAP-Hosting suffered a data breach that exposed over 60GB of data containing 746k unique email addresses. The breach also contained support chat logs, IP addresses, names, purchases, physical addresses and phone numbers.
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 ZAP-Hosting breach exposed and what each item actually enables:
Personal correspondence can be used for blackmail or social engineering, and often contains other sensitive details you have forgotten sharing.
Home addresses feed people-search and data-broker sites, which republish them publicly. They also make phishing far more convincing and, in the worst cases, enable real-world harassment.
Enables SIM-swap attacks (hijacking your number to intercept SMS codes), smishing, and voice scams that appear to come from your bank.
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.
Reveals your approximate location and internet provider, which adds credibility to targeted scams.
Also listed in this breach: Browser user agent details, Chat logs, Email addresses, IP addresses, Names, Phone numbers, Physical addresses, Purchases.
What to do if you were affected
These steps are ordered for this specific breach — the most urgent action given what leaked comes first.
- Private messages: Consider what was discussed on this service and whether anything needs changing (shared passwords, personal disclosures).
- Home addresses: Get your address removed from data brokers — they re-list roughly every four months, so this needs repeating.
- Phone numbers: Move two-factor authentication off SMS to an authenticator app or passkey, and add a port-out PIN with your mobile provider.
- 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.
This breach put your details on data-broker sites
Because ZAP-Hosting exposed home addresses, this is one of the breaches that feeds people-search and data-broker sites. Those sites scrape leaked databases, combine them with public records, and republish the result as a searchable profile — which is how a single breach turns into a permanent public listing. Removal works, but brokers typically re-list within about four months, so it has to be repeated.
See our broker-by-broker removal guides →
How urgent is this now?
This data has been circulating for around 5 years, which means it has been copied, combined with other leaks and indexed by search tools many times over.
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 ZAP-Hosting breach?
The ZAP-Hosting breach exposed private messages, home addresses, phone numbers, names and usernames, email addresses, ip addresses. Personal correspondence can be used for blackmail or social engineering, and often contains other sensitive details you have forgotten sharing.
How many people were affected by the ZAP-Hosting breach?
Around 746,682 accounts were exposed, making it a mid-sized breach.
What should I do if I had a ZAP-Hosting account?
Consider what was discussed on this service and whether anything needs changing (shared passwords, personal disclosures). 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 ZAP-Hosting breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.
- Was your data in the Fashion Nexus breach? (2018, ~1,279,263 accounts)
- Was your data in the HTH Studios breach? (2018, ~411,755 accounts)
- Was your data in the Regpack breach? (2016, ~104,977 accounts)
- Was your data in the Bourse des Vols breach? (2021, ~1,460,130 accounts)
- Was your data in the Viva Air breach? (2022, ~932,232 accounts)
- Was your data in the Guntrader breach? (2021, ~112,031 accounts)