Fashion Nexus Data Breach (2018): What Was Exposed & What To Do
SourceBreach data provided in part by Have I Been Pwned, used under CC BY 4.0.
The Fashion Nexus Data Breach (2018) (reported July 9, 2018) exposed Browser user agent details, Dates of birth, Email addresses and Genders belonging to roughly 1.3M people. If you have an account with them, your information may now be circulating on the open web and with data brokers. Here’s exactly what happened, how to check if you were affected, and what to do next.
Inside the incident
The breach came to light on 9 July 2018. Public information at the time stated that 1.4 million records were involved, containing browser user agent details, dates of birth, email addresses, genders, IP addresses, names, passwords, and phone numbers. Passwords appeared in a mix of salted MD5, SHA-1, and unsalted MD5 formats. When asked for a public statement, the company responded with a single word: “No.” No further details on the method of access, duration of exposure, or total number of affected accounts have been released.
How a breach like this happens
Incidents involving ecommerce platforms commonly begin with an attacker locating an unprotected database, an exposed administrative interface, or an application vulnerability that allows bulk data extraction. Once inside, the attacker can copy files containing customer records and authentication data. Weak or outdated password hashing increases the chance that any obtained credentials can later be used elsewhere. Such events are frequently discovered only after the data appears on public forums or is offered for sale.
Fashion Nexus and its sector
Fashion Nexus operated as a UK ecommerce business whose sites handled online retail transactions and customer accounts. Companies in this sector routinely collect names, contact information, dates of birth, and login credentials to process orders and manage user profiles. A breach at one such firm is consequential because the same data types are used across many similar platforms, raising the possibility that exposed credentials could be tested against other services.
The information in question
The records reported as exposed included browser user agent details, dates of birth, email addresses, genders, IP addresses, names, passwords, and phone numbers. The exact presence of additional fields such as physical addresses remains unconfirmed in available reports. Password storage relied on older hashing methods that vary in resistance to modern recovery techniques.
The real-world impact
Individuals whose details appeared in the records face the possibility that their email addresses and passwords could be used in attempts to access other online accounts. Phone numbers and dates of birth can support targeted phishing or identity-verification fraud. For the organisation, the incident created reputational and regulatory exposure typical of any large-scale loss of customer authentication data, though the long-term effects on the business have not been publicly quantified.
What to do if you're exposed
Change passwords on any accounts that reuse the exposed credentials, starting with email and retail sites. Enable two-factor authentication where available and monitor statements or login alerts for unusual activity. Readers can run a free exposure scan of their email address against known breach data to check whether their information appears in this or other incidents.
AICompiled with AI assistance from public sources and published under our editorial standards.
How this breach connects
More recent breaches
IIMJobs Data Breach (2018)BannerBit Data Breach (2018)BlankMediaGames Data Breach (2018)Roll20 Data Breach (2018)Latest breaches
Read GalaxyWarden’s full analysis of the Fashion Nexus Data Breach (2018) →
Verified breach. Breach data provided in part by Have I Been Pwned, used under CC BY 4.0.
Breach listings — particularly those originating from ransomware or leak sites — are third-party claims that may be unverified, incomplete, or inaccurate. A listing does not by itself confirm that a breach occurred or that any specific data was exposed. Severity is an automated assessment, not a definitive rating. Verification status is shown where available.
Attributions to threat groups and methods reflect public reporting and, in some cases, unverified claims made by the groups themselves; they may be incomplete or later revised. Recent Breaches and GalaxyWarden are independent and are not affiliated with, and do not endorse, any company or group named on this page. This information is aggregated from public sources for awareness only and is not legal, security, or investment advice.