Home › Intelligence › Brief
BREACH BRIEF🟠 High Breach

Morele.net Breach Exposes 2.47M Customer Records Including Password Hashes

In October 2018, Polish e‑commerce site Morele.net suffered a breach that leaked 2.5 million email addresses, names, phone numbers and password hashes. The exposure of credential data highlights gaps in password protection and access controls, underscoring the need for robust identity‑management evidence for audit readiness.

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

Morele.net Breach Exposes 2.47M Customer Records Including Password Hashes

What Happened – In October 2018 the Polish e‑commerce site Morele.net suffered a data breach that leaked 2,467,304 unique email addresses, names, phone numbers and passwords stored as MD5‑crypt hashes.

Why It Matters for Trust & Control Assurance

  • The exposure of credential hashes signals a lapse in password‑storage and access‑control safeguards that a continuous control‑assurance program is built to detect and remediate.
  • Demonstrating robust identity‑management controls (e.g., modern hashing, privileged‑access monitoring) provides defensible evidence for audit readiness under data‑protection regulations.
  • Ongoing monitoring and evidence collection around credential protection helps prove due‑diligence to regulators and partners.

Who Is Affected – Retail and e‑commerce operators handling EU personal data, as well of any downstream services that integrated with Morele.net’s customer database.

Recommended Actions

  • Upgrade password hashing to salted, memory‑hard algorithms such as bcrypt or Argon2.
  • Deploy continuous monitoring of privileged access and retain immutable logs for forensic analysis.
  • Map credential‑protection controls to your audit framework and collect evidence in a Trust Center.

Technical Notes – The breach disclosed email addresses, full names, phone numbers and password hashes (MD5‑crypt). The exact attack vector was not disclosed, but the use of weak hashing indicates inadequate credential‑storage controls. Source: [Have I Been Pwned – Morele.net breach]

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

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

From the Verisq platform · Trust Operations

Could you prove your access controls held up here?

Credential and access failures map directly to identity and access-control requirements in every major framework. The Verisq AI Trust Operations platform shows where your evidence is thin before an auditor — or an attacker — finds out.

Explore the Verisq AI Trust Operations platform →