2
Published signals
currently linked to this company
Company intelligence
zara.com
This company page brings together public reporting currently associated with Zara. It reflects signals published by Shadow Tier and should not be read as a complete incident history.
Company links
2
currently linked to this company
0
recent published signals
1
recent published signals
2
confidence classifications
July 22, 2026
most recent published signal
Explore related intelligence
Based on all published signals currently linked to Zara. Affected countries come from victim data; the company country above remains a separate profile fact. Counts describe this reporting set, not overall incident prevalence.
Company signals
On May 8, 2026, Zara, a brand of the Spanish fashion giant Inditex, confirmed a data breach that exposed personal information of approximately 197,000 customers. The incident was attributed to the ShinyHunters extortion group, which exploited compromised authentication tokens of a former third-party analytics provider, Anodot, to access customer data. Exposed data included email addresses, geographic locations, purchase history, and support tickets, though Inditex stated that names, passwords, addresses, and payment information were not compromised.
The Zara data breach exposed 197,376 records including Email addresses, Geographic locations, Purchases, Support tickets. This breach has been verified by HaveIBeenPwned. Affected users should check HaveIBeenPwned.com and take immediate steps to protect their accounts. 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 . The following data types were included in the breach: If you had an account with Zara, take these steps immediately: Check if your account was affected at HaveIBeenPwned.com Watch for phishing emails that reference the breach or impersonate the affected company Be alert for social engineering attempts using your exposed personal information Enable two-factor authentication on the affected service if available Consider using a password manager to generate unique passwords for each service Sherlock Forensics investigates data breaches for organizations. We determine scope of exposure, identify attack vectors, preserve evidence for legal proceedings and help you meet notification requirements. 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 . Use a password manager to generate and store strong, unique passwords for all your accounts. 1Password helps protect your data with industry-leading security. In Nederland adviseert een samenwerking van publieke en private organisaties mensen over hun online veiligheid op veiliginternetten.nl. If you haven’t already changed the password affected by this breach, do so immediately on every account where it was used. Wherever 2FA is supported, add an extra layer of security to your account.
FAQ
It combines a reviewed organization profile with all current published Shadow Tier signals explicitly linked to Zara.
No. A signal must contain a reliable company connection and meet the publication criteria; incidental or ambiguous mentions are excluded.
The page follows current published reporting. Counts change as new evidence is added, classifications are reviewed, or older signals leave the reporting window.