Hiapk

hiapk.com

13,843,251
Exposed Records
Jan 2014
Breach Date
12 years ago
Easy to Crack
Password Risk
Information Technology industry
Information Technology
Industry
Added to XposedOrNot on October 12, 2024 · #108 of 763 breaches by records exposed

About This Breach

The HIAPK Data Breach, alleged to have occurred around 2014, involved the compromise of data for approximately 13.8 million unique subscribers from the Chinese Android store HIAPK. The data includes usernames, email addresses, and salted MD5 password hashes. Although the data appears to be legitimate, it has been flagged as "unverified" due to challenges in conclusively verifying the breach's specifics within China.

Data Exposed

Email addresses
Usernames
Passwords

Breach Details

Breach Type Data Breach
Searchable Yes
Verified No
Sensitive Data No
Reference No reference available

Frequently Asked Questions

When did the Hiapk data breach happen?

Hiapk was breached in Jan 2014. The breach was added to the XposedOrNot index on October 12, 2024.

How many records were exposed in the Hiapk breach?

13,843,251 records were exposed, making it the #108 largest of the 763 breaches in our index.

What data was exposed in the Hiapk breach?

The exposed data includes: Email addresses, Usernames, Passwords.

What should I do if I was affected by the Hiapk breach?

Change your password on the affected service (and anywhere you reused it), turn on two-factor authentication, and set up free breach alerts on XposedOrNot so you know the moment your email appears in a new breach.

What Should You Do?

Urgent

Change Your Passwords

Update your password immediately, using 12+ characters with numbers and symbols.

High Priority

Enable Two-Factor Authentication

Add 2FA on all supported accounts using an authenticator app like Google Authenticator or Authy.

Recommended

Monitor Your Accounts

Set up login alerts and review account activity regularly for suspicious access.

Best Practice

Use a Password Manager

Never reuse passwords: use a password manager to generate unique ones for each account.