Home › Intelligence › Brief
BREACH BRIEF🟠 High Breach

LuLu Hypermarket Data Breach Exposes Nearly 2.8 M Customer Records

LiveThreat™ Intelligence · 📅 October 07, 2026· 📰 haveibeenpwned.com
🟠
Severity
High
BR
Type
Breach
🎯
Confidence
HIGH
🏢
Affected
3 sector(s)
✅
Actions
3 recommended
📰
Source
haveibeenpwned.com

LuLu Hypermarket Data Breach Exposes Nearly 2.8 M Customer Records

What Happened

In July 2024 the Emirati retailer LuLu Hypermarket suffered a breach that exposed 2,796,835 customer accounts. An initial set of ~190 k email addresses and phone numbers was posted on a hacking forum, followed in August by a backup dump from October 2022 containing an additional 2.6 M unique email addresses, names, physical addresses, order histories, and PBKDF2 password hashes.

Why It Matters for Compliance & Audit Readiness

  • Demonstrates the need for continuous monitoring of third‑party data stores and rapid detection of unauthorized exfiltration.
  • Highlights the importance of maintaining defensible evidence of encryption practices (e.g., PBKDF2) and verifying that password hashing meets current NIST guidelines.
  • Reinforces the requirement for documented incident‑response playbooks that include vendor‑notification timelines and breach‑impact assessments for audit trails.

Who Is Affected

  • Retail and e‑commerce operators handling large consumer databases.
  • Third‑party logistics or payment processors integrated with LuLu’s storefront.
  • Customers in the United Arab Emirates and any region where LuLu ships products.

Recommended Actions

  • Review any data‑sharing agreements or APIs that connect your environment to LuLu’s platforms.
  • Validate that monitoring controls (file integrity, anomalous outbound traffic alerts) are active and tuned for large data extracts.
  • Request a detailed incident‑response disclosure from LuLu, including timelines, root‑cause analysis, and remediation steps.

Technical Notes

  • Attack vector: Unauthorized access to LuLu’s customer database, likely via compromised credentials or insufficiently segmented storage, leading to bulk data exfiltration.
  • CVEs: None reported in the public disclosure.
  • Data types exposed: Email addresses, names, phone numbers, physical addresses, purchase histories, PBKDF2 password hashes.

Source: https://haveibeenpwned.com/api/v3/breach/LuLu

📰 Original Source
https://haveibeenpwned.com/api/v3/breach/LuLu ↗

This LiveThreat Intelligence Brief is an independent analysis. Read the original reporting at the link above.

From the Verisq platform · Vendor Risk Hub

Point-in-time vendor reviews miss incidents like this.

Verisq AI Trust Operations replaces the annual questionnaire with continuous third-party monitoring — so vendor exposure becomes audit evidence, not a once-a-year guess.

See how Verisq AI Trust Operations works →