Ancestry Data Breach (2015): What Was Exposed & What To Do
SourceBreach data provided in part by Have I Been Pwned, used under CC BY 4.0.
The Ancestry Data Breach (2015) (reported November 7, 2015) exposed Email addresses and Passwords belonging to roughly 298K 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.
Breaking down the breach
The incident occurred in November 2015 and affected the RootsWeb platform. Records state that 298,000 email addresses and passwords stored in plain text were present in the file discovered in late 2017. No additional information on the timing of the initial compromise, the number of records accessed, or the attack vector has been disclosed.
How a breach like this happens
Incidents involving the exposure of email addresses and passwords commonly begin with the compromise of a web application or database server. Attackers may exploit unpatched software, weak authentication controls, or stolen administrative credentials to reach stored user data. Once inside, they can extract credential files and later distribute them through public or private channels. The presence of plain-text passwords indicates that the storage system did not apply hashing or salting at the time of the breach.
Ancestry and its sector
Ancestry operates online genealogy platforms that allow users to build family trees and share historical records. These services routinely collect and retain contact information, login credentials, and detailed personal and familial data submitted by subscribers. A breach at such a company is consequential because the records often link individuals across generations and can contain sensitive biographical details that persist long after an account is closed.
The information in question
The only data types explicitly named in connection with the 2015 RootsWeb incident are email addresses and passwords. Organisations of this type typically hold additional categories of personal information, including names, dates of birth, locations, and family relationships. The precise contents of the exposed file beyond the two named fields remain unconfirmed in available records.
Why it matters
Email addresses paired with passwords can be tested against other online accounts, increasing the chance of credential stuffing elsewhere. For a genealogy service, the exposure also raises the possibility that family-linked data could be combined with the credentials, though the exact scope of any such linkage is not documented. The organisation faces reputational and regulatory consequences typical of any large-scale credential disclosure.
What to do if you're exposed
Individuals who believe their information may have been involved should change passwords on Ancestry and any other sites where the same credentials were used. Enabling multi-factor authentication on accounts that support it reduces the value of exposed passwords. Monitoring email for unusual login attempts and reviewing account activity on linked services are standard next steps. Readers can run a free exposure scan of their email address to check whether their information has surfaced in known breach data.
- Change the affected password and any reused passwords immediately.
- Enable multi-factor authentication wherever available.
- Review recent account activity for signs of unauthorised access.
- Monitor email inboxes for unexpected password-reset requests.
AICompiled with AI assistance from public sources and published under our editorial standards.
How this breach connects
More recent breaches
Trillian Data Breach (2015)QuinStreet Data Breach (2015)Aternos Data Breach (2015)DaniWeb Data Breach (2015)Latest breaches
Read GalaxyWarden’s full analysis of the Ancestry Data Breach (2015) →
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.