[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f2npqw5xssml7g":3},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":7,"domain":9,"breachDate":10,"addedDate":11,"modifiedDate":12,"contentUpdatedAt":12,"source":13,"sourceUrl":14,"sourceUrls":15,"pwnCount":17,"affectedCount":17,"affectedCountStatus":18,"affectedCountLowerBound":19,"affectedCountUnit":20,"hasEnglishDescription":4,"severity":21,"dataClasses":22,"description":26,"seoTitle":27,"seoTitleEn":28,"seoDescription":27,"seoDescriptionEn":29,"logoUrl":30,"isVerified":4,"isSensitive":4,"isSpamList":31,"isMalware":31,"company":32},"68e3266eda11adda488250db","ancestry","RootsWeb 2015 Data Breach","ancestry.com","2015-11-07T00:00:00.000Z","2017-12-24T04:28:45.000Z","2026-07-29T11:13:00.741Z","Authenticated RootsWeb credential corpus with official notice","https:\u002F\u002Foag.ca.gov\u002Fsystem\u002Ffiles\u002FRootsWeb%20Breach%20Notice%20_%20Combined%20_0.pdf",[14,16],"https:\u002F\u002Fwww.jdsupra.com\u002Flegalnews\u002Fancestry-com-server-exposes-300-000-66007\u002F",297806,"known",null,"records","High",[23,24,25],"Email addresses","Plaintext passwords","Usernames","\u003Cp>\u003Cstrong>The 2015 RootsWeb data breach\u003C\u002Fstrong> is a credential corpus associated with November 7, 2015, and discovered by Ancestry in 2017 in an old RootsWeb server file. It must not be presented as a direct breach of Ancestry DNA, family-tree, payment, or primary Ancestry systems.\u003C\u002Fp>\u003Cp>The external source reports 297,806 accounts and local search contains 297,783 records, a difference of 23. The three reported fields are emails, usernames, and plaintext passwords. Neither measure means unique people, active RootsWeb or Ancestry customers, or rows containing every field together.\u003C\u002Fp>\u003Cp>DNA, family-tree content, payment cards, Social Security numbers, physical addresses, and health data are not classes in this record. A match does not establish identity, a RootsWeb or Ancestry account, a family relationship, password ownership or currentness, field co-occurrence, account takeover, or misuse.\u003C\u002Fp>\u003Cp>If the old password genuinely belonged to the person and was reused elsewhere, it should be replaced with a unique password. Messages using family-tree invitations, archive access, or security notices should be verified through an independent official channel.\u003C\u002Fp>","","RootsWeb 2015 Data Breach (297.8 Thousand Records)","RootsWeb 2015 Data Breach. 297.8 Thousand records were reported. Reported data: Email addresses, Plain text passwords, Usernames. Review the scope, risks, and…","\u002Fuploads\u002Flogo\u002Fancestry_com.webp",false,{"name":33,"sector":34,"country":35,"website":9,"websiteArchiveUrl":27,"websiteStatus":27,"websiteCheckedAt":19},"Ancestry \u002F RootsWeb","Genealogy","United States"]