Data breaches → Zara
Was your data in the Zara breach?
2026 · zara.com · ~197,376 accounts exposedModerate severity · 5/10
Zara (zara.com) suffered a data breach in 2026 that exposed around 197,376 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 April 2026, the fashion brand Zara was among a number of organisations targeted by the ShinyHunters extortion group as part of their "pay or leak" campaign. The group claimed the breach was related to a compromise of the Anodot analytics platform and subsequently published a terabyte of data allegedly including 95M support ticket records. The data contained 197k unique email addresses alongside product SKUs, order IDs and the market the support ticket originated in. Zara's parent company Inditex advised that the incident didn't affect passwords or payment information.
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 Zara breach exposed and what each item actually enables:
Reveals where you live, work or travel, which supports both targeted scams and physical-safety risks.
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.
Also listed in this breach: Email addresses, Geographic locations, Purchases, Support tickets.
What to do if you were affected
These steps are ordered for this specific breach — the most urgent action given what leaked comes first.
- Location data: Review location sharing on the accounts you still hold with this service.
- 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 Zara breach?
The Zara breach exposed location data, email addresses. Reveals where you live, work or travel, which supports both targeted scams and physical-safety risks.
How many people were affected by the Zara breach?
Around 197,376 accounts were exposed, making it a mid-sized breach.
What should I do if I had a Zara account?
Review location sharing on the accounts you still hold with this service. 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 Zara breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.
- Was your data in the Samsung Germany Customer Tickets breach? (2025, ~216,333 accounts)
- Was your data in the Baydöner breach? (2026, ~1,266,822 accounts)
- Was your data in the SuperDraft breach? (2024, ~300,187 accounts)
- Was your data in the Tibber breach? (2024, ~50,002 accounts)
- Was your data in the GiveSendGo breach? (2022, ~89,966 accounts)
- Was your data in the Z-lib breach? (2024, ~9,737,374 accounts)