[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$f36xqbhgg0vopg":3},{"success":4,"breach":5},true,{"_id":6,"name":7,"title":8,"slug":9,"domain":10,"breachDate":11,"addedDate":12,"modifiedDate":13,"contentUpdatedAt":13,"source":14,"sourceUrl":15,"sourceUrls":16,"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":31,"isSensitive":4,"isSpamList":31,"isMalware":31,"company":32},"68e3266eda11adda4882521d","HIAPK","HiAPK Alleged Data Exposure","hiapk","hiapk.com","2014-01-01T00:00:00.000Z","2018-04-01T07:13:44.000Z","2026-07-29T11:13:00.741Z","Third party breach","https:\u002F\u002Fdata-wells.niamonx.io\u002FBreach\u002FHiAPK",[15],13873674,"known",null,"email_identifiers","Critical",[23,24,25],"Email addresses","Passwords","Usernames","\u003Cp>\u003Cstrong>The circa-2014 dataset attributed to HiAPK\u003C\u002Fstrong> is catalogued by public breach source as a corpus whose data appears legitimate but whose service attribution remains unverified. public breach source reports 13,873,674 unique subscribers or emails and the collection-level classes usernames, emails, and salted MD5 password hashes. January 1 is only a catalogue marker for the approximate year, not an incident day.\u003C\u002Fp>\u003Cp>Another derivative analysis reports 12.3 million unique accounts, 25.5 million data points, 12.3 million emails, 9.9 million nicknames, and password material for only 3.3 million. This shows corpus-version and field-prevalence differences; a username and hash should not be assumed present with every email. Salted MD5 is not plaintext, and no particular password is proven cracked or reused.\u003C\u002Fp>\u003Cp>No HiAPK data is locally searchable. The record does not identify anyone as a HiAPK, China, or Android-store user; it cannot establish app use, username, password hash, field co-occurrence, password ownership, compromise, or misuse. Until attribution is verified, person-level results must remain private and carry a source-confidence warning.\u003C\u002Fp>","","HiAPK Alleged Data Exposure (13.9 Million Email Identifiers)","HiAPK Alleged Data Exposure. 13.9 Million email identifiers were reported. Reported data: Email addresses, Passwords, Usernames. Review the scope, risks, and…","\u002Fuploads\u002Flogo\u002Fhiapk_com.webp",false,{"name":33,"sector":34,"country":35,"website":10,"websiteArchiveUrl":27,"websiteStatus":27,"websiteCheckedAt":19},"HiAPK","Technology","China"]