Cybersecurity1 hr ago

Zara Email Leak Traced to Compromised Anodot Credentials

ShinyHunters leaked 197,400 Zara customer emails after stealing Anodot tokens to query BigQuery, exposing order and support data but no passwords or payment details.

Peter Olaleru/3 min/GB

Cybersecurity Editor

TweetLinkedIn
Zara Email Leak Traced to Compromised Anodot Credentials
Source: HaveibeenpwnedOriginal source

TL;DR: In April 2026, ShinyHunters leaked 197,400 Zara customer email addresses after stealing Anodot credentials to query BigQuery databases. Inditex confirmed the breach originated from a former technology provider and said no passwords or payment data were exposed.

Context

Inditex, parent of Zara, disclosed that unauthorized access came through a third‑party analytics vendor it no longer uses. The attacker gained entry to BigQuery instances hosting order and support data, extracting a 140 GB archive that included email addresses, product SKUs, order IDs, geographic locations and support tickets. No names, passwords, payment details or phone numbers were stored in the affected tables, according to the company.

Key Facts

- 197,400 unique email addresses were exposed, as verified by Have I Been Pwned. - The leak also contained order IDs, SKUs, purchase history and support tickets, enabling detailed profiling of shopping habits. - ShinyHunters claimed the intrusion used compromised Anodot authentication tokens to move from the analytics platform into BigQuery, a technique they have reused against dozens of other firms. - The group posted a Tor‑based leak site demanding payment, citing “incredible patience” and referencing prior victims such as Vimeo, Rockstar Games and the European Commission. - Inditex applied its security protocols, notified authorities and stated that operations and customer services remain unaffected.

What It Means

The incident shows how a single credential compromise in a SaaS analytics tool can cascade into broad data exposure across multiple customer‑facing services. Attackers exploited valid cloud accounts (MITRE ATT&CK T1078.004) to run unauthorized queries, then exfiltrated results via standard BigQuery export functions. Defenders should treat token‑based access to analytics platforms as a high‑value target and enforce strict controls.

Mitigations / What Defenders Should Do - Rotate and invalidate all Anodot API keys and service accounts; enforce MFA and short‑lived tokens. - Restrict BigQuery access to approved networks or VPC Service Controls and disable public endpoints. - Enable detailed audit logging for BigQuery job submissions and token usage; create SIEM alerts for anomalous query volumes or unusual geographic origins. - Apply the principle of least privilege: service accounts should only have read access to required datasets. - Review third‑party vendor contracts for security clauses and require regular penetration testing of connected SaaS apps. - Monitor dark‑web and extortion sites for leaked credentials linked to your organization.

Watch for follow‑up extortion notices from ShinyHunters and any updates from Inditex on provider remediation and token rotation.

TweetLinkedIn

More in this thread

Reader notes

Loading comments...