ShinyHunters Leak Exposes Data of 197,000 Zara Customers via Third-Party Provider
Inditex disclosed that unauthorized access to databases hosted by a former third-party technology provider exposed data tied to nearly 197,000 Zara customers. The compromised records reportedly included about 197,400 unique email addresses, order IDs, product SKUs, geographic market information, purchase history, and customer support ticket data. Inditex said the incident did not affect names, passwords, payment details, postal addresses, or phone numbers, and added that Zara’s own operations and internal systems were not impacted.
The breach has been linked by Have I Been Pwned to the ShinyHunters extortion group’s April 2026 “pay or leak” campaign. According to the reporting, the attackers claimed they gained access through compromised Anodot authentication tokens and exfiltrated data from BigQuery environments, including a broader archive that allegedly contained up to 95 million support ticket records. After failed extortion attempts, the group reportedly published the stolen data, while Inditex said it activated security protocols and began notifying relevant authorities.

Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
5 events from the most recent confirmed update back to the earliest known activity.
Inditex says nearly 197,000 Zara customers were affected
On 2026-05-08, reporting said Inditex disclosed that nearly 197,000 Zara customers were affected by unauthorized access to databases hosted by a former third-party provider. The company said names, passwords, payment details, addresses, and phone numbers were not affected, and that it had activated security protocols and begun notifying relevant authorities.
HIBP lists Zara breach and links it to 197,000 exposed email addresses
On 2026-05-08, Have I Been Pwned added the Zara breach, stating that about 197,000 unique email addresses were exposed in a broader leaked dataset. HIBP linked the incident to ShinyHunters' April 2026 campaign and noted the broader leak allegedly contained 95 million support ticket records.
ShinyHunters publishes Zara data after failed extortion attempts
After unsuccessful extortion attempts in April 2026, ShinyHunters published allegedly stolen Zara-related data. Reports said the leak included support ticket records, email addresses, order IDs, product SKUs, market information, and purchase history.
Inditex discloses contractor-hosted data leak affecting Zara customers
By 2026-04-16, Inditex had flagged a data leak involving databases hosted by a former third-party technology provider and said core client records were safe. The company stated its own operations and systems were not impacted.
ShinyHunters targets Zara in April 2026 pay-or-leak campaign
In April 2026, Zara was identified as one of several organizations targeted by the ShinyHunters extortion group. The actor claimed the breach was linked to compromised Anodot authentication tokens used to access BigQuery data and said it stole a large archive of data.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
3 references tracked. Mallory keeps watching after this page renders.
Zara Data Breach: 197,000 Customers Exposed in Third-Party Security Incident
securityaffairs.com
Open sourceHave I Been Pwned: Zara Data Breach
haveibeenpwned.com
Open sourceInditex flags contractor data leak, says client records safe - FashionNetwork
ww.fashionnetwork.com
Open sourceSee the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.


