LiveBreach Intelligence: data breaches, leaks & ransomware, tracked as they surfaceOngoing protection: GalaxyWarden →
Recent BreachesData breach tracker

Recent Breaches › Romwe Data Breach (2018)

CRITICAL severityConfirmedHow we verify

Romwe Data Breach (2018): What Was Exposed & What To Do

RBRecent Breaches Breach Intelligence·June 1, 2018

SourceBreach data provided in part by Have I Been Pwned, used under CC BY 4.0.

Romwe Data Breach (2018)

Reported June 1, 2018. Approximately 19.5M people affected.

CRITICAL
Severity
19.5M
People affected
6
Data types exposed
June 1, 2018
Disclosed
ShareXLinkedInFacebookRedditWhatsAppTelegram

The Romwe Data Breach (2018) (reported June 1, 2018) exposed Geographic locations, IP addresses, Names and Passwords belonging to roughly 19.5M 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.

Severity & verification
CRITICAL severityConfirmed
Account credentials exposed.
Corroborated by an official disclosure or a verified breach feed.
Was your email in the Romwe Data Breach (2018) breach?
19.5M accounts were exposed here. See if yours is one — and every other breach it’s in. 15-sec check, no card.

By running your scan you agree to the Terms and Conditions and the Privacy Policy, and to GalaxyWarden emailing you the results of this scan.

In June 2018, reports surfaced that the online retailer Romwe had suffered a data breach affecting 19.5 million customers. The incident, which took place in mid-2018, resulted in customer records appearing for sale on underground forums, with the dataset later supplied to Have I Been Pwned by dehashed.com. The breach exposed names, phone numbers, email addresses, IP addresses, geographic locations, physical addresses, and passwords stored as salted SHA-1 hashes.

Breaking down the breach

Public records indicate the breach was first noted around 1 June 2018. The compromised dataset contained records for 19.5 million individuals. No official statement from the company detailing the intrusion method, exact date of compromise, or duration of unauthorized access has been referenced in available reporting. The data subsequently circulated on online marketplaces before being shared with breach-tracking services.

How a breach like this happens

Incidents involving retail customer databases often stem from unauthorized access to web servers or backend systems that store account information. Attackers may exploit unpatched software, weak authentication controls, or stolen credentials to reach these repositories. Once inside, they can copy large volumes of records without immediate detection. The subsequent sale of the data on forums is a common pattern, allowing the material to reach multiple buyers over time.

Who is Romwe?

Romwe is a Hong Kong-based online fashion retailer that sells clothing and accessories directly to consumers through its website. Like similar e-commerce platforms, it collects and retains customer details necessary for order processing, shipping, and account management. A breach at such a company is consequential because the stored information typically includes identifiers and contact data that remain valid for years after the original transaction.

What data was at risk

The records reported as exposed include the following elements:

Exact confirmation of every field present in the full dataset remains limited to the descriptions provided by sources that obtained the material.

The real-world impact

Individuals whose information appeared in the dataset face the possibility of targeted phishing messages, unsolicited marketing, or attempts to access other accounts if the same passwords were reused elsewhere. Hashed passwords require additional effort to reverse, yet older hashing methods can be processed offline once the data is obtained. For the organization, the incident created reputational and operational consequences typical of large-scale retail exposures, including potential regulatory scrutiny and customer support demands.

What to do if you're exposed

Anyone who used Romwe should change the password associated with that account and any other service where the same credentials were reused. Enable multi-factor authentication on important accounts and monitor bank and email statements for unusual activity. Individuals can also run a free exposure scan of their email address against known breach datasets to determine whether their information has appeared in this or other incidents.

AICompiled with AI assistance from public sources and published under our editorial standards.

Editorial & sourcing policy
Recent Breaches is a breach-monitoring service and news aggregator. We do not exfiltrate, host, purchase, or redistribute stolen data, and we do not hold the data claimed in leak-site listings. Incidents are compiled from publicly accessible sources and threat-intelligence platforms and are reported as claims attributed to their source. We promptly correct or remove material shown to be inaccurate — write to support@galaxywarden.com or press@recentbreaches.com.
Check if you’re exposed →

How this breach connects

Company

Method

CompanyRomwe security record
73/100
DoxxScan™ · Moderate doxx risk
C- 64Below-average record

1 reported incident on record.

See Romwe’s full breach history →

More recent breaches

IIMJobs Data Breach (2018)December 31, 2018BannerBit Data Breach (2018)December 29, 2018BlankMediaGames Data Breach (2018)December 28, 2018Roll20 Data Breach (2018)December 26, 2018

Latest breaches

Read GalaxyWarden’s full analysis of the Romwe 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.

ShareXLinkedInFacebookRedditWhatsAppTelegram