Data breaches → IndiHome
Was your data in the IndiHome breach?
2019 · indihome.co.id · ~12,629,245 accounts exposedHigh severity · 6/10
IndiHome (indihome.co.id) suffered a data breach in 2019 that exposed around 12,629,245 accounts. If you had an account, some of your personal data may be circulating in leaked databases. The fastest way to know is to check your own email — free, in about 30 seconds, no password required.
What happened
In mid-2021, reports emerged of a data breach of Indonesia's telecommunications company, IndiHome. Over 26M rows of data alleged to have been sourced from the company was posted to a popular hacking forum and contained 12.6M unique email addresses alongside names, IP addresses, genders and geographic locations. The most recent data was stamped as being recorded in November 2019.
Breach details sourced from Have I Been Pwned, the industry-standard breach database. Risk analysis by Nullivo.
What was exposed, and why it matters
Not all breaches carry the same risk — what matters is which fields leaked. Here is what the IndiHome breach exposed and what each item actually enables:
Reveals where you live, work or travel, which supports both targeted scams and physical-safety risks.
Links this leak to your other accounts — a reused username lets anyone build a profile of you across platforms.
Puts you on spam and phishing lists, and confirms to attackers that you hold an account with this service — which makes impersonation emails more believable.
Reveals your approximate location and internet provider, which adds credibility to targeted scams.
Also listed in this breach: Device information, Email addresses, Genders, Geographic locations, IP addresses, Names.
What to do if you were affected
These steps are ordered for this specific breach — the most urgent action given what leaked comes first.
- Location data: Review location sharing on the accounts you still hold with this service.
- Names and usernames: Search your usual username to see what else it exposes, and use distinct handles for sensitive accounts.
- Email addresses: Treat any message referencing this service with suspicion, and never act on links in unexpected emails.
- IP addresses: No direct action needed, but be wary of anyone quoting your location as “proof” of identity.
- Check whether your own email appears in this breach — run a free scan to confirm before you spend time on the steps above.
How urgent is this now?
This breach is over 7 years old. Old credentials still cause harm — leaked passwords from a decade ago are still tried against new accounts every day.
Remember: a breach can't be "un-leaked" — once a database is out, it exists in countless copies. The goal is to make the leaked data useless: change what can be changed, lock down what can't, and remove what has been republished.
Frequently asked questions
What data was exposed in the IndiHome breach?
The IndiHome breach exposed location data, names and usernames, email addresses, ip addresses. Reveals where you live, work or travel, which supports both targeted scams and physical-safety risks.
How many people were affected by the IndiHome breach?
Around 12,629,245 accounts were exposed, making it a very large breach by any measure.
What should I do if I had a IndiHome account?
Review location sharing on the accounts you still hold with this service. You can check whether your own email appears in this breach with a free Nullivo scan — no password required.
Breaches that exposed similar data
If the IndiHome breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.
- Was your data in the ai.type breach? (2017, ~20,580,060 accounts)
- Was your data in the Tigo breach? (2023, ~700,394 accounts)
- Was your data in the 8fit breach? (2018, ~15,025,407 accounts)
- Was your data in the Wishbone (2020) breach? (2020, ~9,705,172 accounts)
- Was your data in the Dunzo breach? (2020, ~3,465,259 accounts)
- Was your data in the Pluto TV breach? (2018, ~3,225,080 accounts)