RedDoorz Data Breach (2020)
Budget hotel and accommodation platform.
What this rating measures
The Index rates how dangerous a breach is right now rather than how large it was. It values each exposed field on its own, ages each one according to what that field is, and models what the assembled set lets an attacker do.
It is read against what is observed circulating, not what was announced. Five bands run from Low through Guarded, Elevated and High to Severe.
Every rating carries a status. Observed means it rests on fields seen circulating. Observed minimum means at least that much was seen, so read it as a floor. Provisional means the field list comes from breach catalogues and is not yet verified. How sure we are of the evidence is shown separately, and it never lowers the rating. How the Index works →
Includes a date of birth alongside enough detail to single out one person. A date of birth cannot be changed.
- Circulating
- 5,890,277 email addresses
- Field types
- 7 seen
- Breach date
- Sep 2020
- Observed as of
- 2026-11-09
a year laterBreach5 years laterListed in breach cataloguesObserved · scored
What data was exposed
How this data can be used against you
Social engineering
Contact details plus enough context for a convincing approach.
Account access
Account material that is weakened or incomplete.
Identity
No usable identity package in what circulates.
Physical targeting
No usable location detail in what circulates.
Financial
No usable financial detail in what circulates.
Coercion
Nothing in what circulates is sensitive enough for leverage.
Health
No medical detail in what circulates.
Crypto
Nothing in what circulates is tied to crypto assets.
Three key actions to take
Lock your mobile number
Ask your carrier for a port-out PIN so no one can move your number to a new phone.
Treat messages about RedDoorz with care
Do not act on a call, email or text about this breach. Contact RedDoorz using a number you already have.
If you reused your RedDoorz password, change it there
The stored password is well protected, but a reused one is only as safe as the weakest site that has it.
Check whether you were affected
Most people in a breach like this do not need an engagement. They need to know whether their address is in it, and when it turns up somewhere new. HackNotice does both, free: an Instant Check now, alerts after.
Talk to us about your exposure
If you are exposed in a way that cannot be rotated away, or you are responsible for someone who is, a call establishes what is actually reachable about you and what is worth doing first. No charge for the conversation.
Request a confidential call →The full breach analysis
What happened, what the company reported against what is circulating, the field-by-field record, the actor and the advisory.
- What happened
- Recent developments
- Reported and circulating
- Data points exposed
- Downstream risk
- Principal risk advisory
- Threat actor
- Background
- Data context
How this breach happened
In September 2020, hotel booking platform RedDoorz suffered a data breach exposing 5,890,277 accounts. Attackers obtained an Amazon Web Services access key embedded in a 2015 RedDoorz Android app and used it to reach the customer database. Exposed data included names, email addresses, phone numbers, genders, dates of birth, occupations, and passwords stored as bcrypt hashes. Masked credit-card numbers were not compromised.
What has happened since the breach
RedDoorz notified affected customers and forced password resets after discovering the breach.
What was reported vs. what is circulating
Reported
- Status
- Not yet researched
Circulating
- Observed as of
- 2026-11-09
- Breach date
- Sep 2020
- Volume
- 5,890,277 email addresses
- Fields seen
- 7date of birth, email address, gender, full name, job information (occupation), password (bcrypt hash), phone number
The score is built only on what is seen circulating.
Every exposed field, and how long it stays useful
| Field | Shelf life | In notice | Circulating |
|---|---|---|---|
| Date of Birth | Lasts for years | No | Yes |
| Email Address | Lasts for years | No | Yes |
| Gender | Fades over a few years | No | Yes |
| Full Name | Lasts for years | No | Yes |
| Job Information (occupation) | Fades over a few years | No | Yes |
| Password (bcrypt hash) | Expires fast | No | Yes |
| Phone Number | Fades over a few years | No | Yes |
Shelf life is how long a field stays useful to someone holding it. A password expires fast. A government ID number or a date of birth lasts for years. An address stays useful long after it stops being current.
How attackers can use this data
Exposure creates phishing, travel fraud, impersonation of hotel staff, and physical-security concerns tied to travel patterns and lodging behavior. Booking context makes scams easier to personalize.
Risks for executives and other high-profile people
A travel or hospitality breach: itinerary, loyalty and contact data supports pattern-of-life inference and travel-themed phishing. For a high-profile principal the main risk is credible impersonation and enrichment of existing exposure.
Who is behind this breach
No threat actor has been publicly attributed.
About the company
RedDoorz is a Singapore-based hotel-management and budget-accommodation booking platform operating across Southeast Asia.
Why the company holds this data
Hospitality booking platforms collect traveler names, emails, phone numbers, stay history, booking records, and location-linked data across hotel reservation and customer support systems.
About this record
No reported total is on record for this breach. The circulating figure, 5,890,277 email addresses, is what has been observed in the published data. Circulation was last verified on 2026-11-09. The score was last computed on 2026-11-09. Scores come from the Breach Risk Index, which rates what the exposed fields still let an attacker do, not how large the breach was. Breach records change as evidence does. If you hold a notice, a filing or a dataset observation this page does not reflect, report a correction.