[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f32p9hjm4iss4e":3},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":9,"domain":10,"breachDate":11,"addedDate":12,"publishedAt":13,"modifiedDate":14,"contentUpdatedAt":14,"source":15,"sourceUrl":16,"sourceUrls":17,"pwnCount":13,"affectedCount":13,"affectedCountStatus":20,"affectedCountLowerBound":13,"affectedCountUnit":21,"hasEnglishDescription":4,"contentLocale":22,"availableLocales":23,"translations":25,"severity":28,"dataClasses":29,"description":35,"seoTitle":8,"seoDescription":36,"logoUrl":37,"isVerified":4,"isSensitive":4,"isSpamList":38,"isMalware":38,"company":39},"6a4552525cd1434deece5f47","Hostinger","Hostinger Data Breach","hostinger","hostinger.com","2019-08-23T00:00:00.000Z","2026-07-01T17:45:52.553Z",null,"2026-07-29T11:13:00.741Z","Official Hostinger notice, TechCrunch reporting, and BleepingComputer reporting","https:\u002F\u002Fwww.hostinger.com\u002Fblog\u002Fsecurity-incident-what-you-need-to-know\u002F",[16,18,19],"https:\u002F\u002Ftechcrunch.com\u002F2019\u002F08\u002F25\u002Fweb-host-hostinger-data-breach\u002F","https:\u002F\u002Fwww.bleepingcomputer.com\u002Fnews\u002Fsecurity\u002Fhostinger-data-breach-affects-almost-14-million-customers\u002F","unknown","accounts","en",[22,24],"tr",{"en":26,"tr":27},{"slug":9},{"slug":9},"Unknown",[30,31,32,33,34],"Email addresses","IP addresses","Names","Passwords","Usernames","\u003Cp>\u003Cstrong>The August 2019 Hostinger security incident\u003C\u002Fstrong> involved an unauthorized party accessing a server on August 23, obtaining an authorization token, and escalating access to a REST API server used to query client and account details. Hostinger said the accessed API table held usernames, emails, one-way password hashes, first names, and IP addresses for approximately 14 million users. This is an approximate table population, not exactly 14 million unique emails, people, active customers, or fully populated rows.\u003C\u002Fp>\u003Cp>The official notice does not name the hash algorithm. TechCrunch and BleepingComputer attributed SHA-1 to a customer or support response; that secondary attribution does not establish that any person's password was cracked or reused. Hostinger said payment data was handled by third-party processors and that its investigation found client accounts, websites, domains, hosted emails, and other content unaffected. Those are company investigation findings and do not prove that every listed field co-occurred for every person.\u003C\u002Fp>\u003Cp>No Hostinger data has been imported into local search. This record cannot produce a positive or negative person-level result; it cannot establish Hostinger customer status, site, domain, or email ownership, username, name, IP or password-hash presence, field co-occurrence, or misuse. Hostinger said it reset all client login passwords, restricted the system, and rotated credentials.\u003C\u002Fp>","Hostinger Data Breach. The affected total has not been disclosed. Reported data: Email addresses, IP addresses, Names. Review the scope, risks, and protective…","\u002Fuploads\u002Flogo\u002Fhostinger-official.png",false,{"name":7,"sector":40,"country":41,"website":10,"websiteArchiveUrl":42,"websiteStatus":42,"websiteCheckedAt":13},"Web hosting and domain services","Lithuania",""]