Raaga Data Breach (2025)
Music streaming and entertainment platform focused on Indian content.
What this rating measures
The Index rates how dangerous a breach is right now rather than how large it was. It values each exposed field on its own, ages each one according to what that field is, and models what the assembled set lets an attacker do.
It is read against what is observed circulating, not what was announced. Five bands run from Low through Guarded, Elevated and High to Severe.
Every rating carries a status. Observed means it rests on fields seen circulating. Observed minimum means at least that much was seen, so read it as a floor. Provisional means the field list comes from breach catalogues and is not yet verified. How sure we are of the evidence is shown separately, and it never lowers the rating. How the Index works →
Includes a date of birth alongside enough detail to single out one person. A date of birth cannot be changed.
- Volume
- Count not yet verified
- Field types
- 7 listed
- Breach date
- Dec 2025
Breach- Listed in breach catalogues
What data was exposed
How this data can be used against you
Assessed once the record is scored.
Two key actions to take
Change your Raaga password
Change it anywhere you reused it too, and turn on two-step sign-in.
Treat messages about Raaga with care
Do not act on a call, email or text about this breach. Contact Raaga using a number you already have.
Check whether you were affected
Most people in a breach like this do not need an engagement. They need to know whether their address is in it, and when it turns up somewhere new. HackNotice does both, free: an Instant Check now, alerts after.
Talk to us about your exposure
If you are exposed in a way that cannot be rotated away, or you are responsible for someone who is, a call establishes what is actually reachable about you and what is worth doing first. No charge for the conversation.
Request a confidential call →The full breach analysis
What happened, what the company reported against what is circulating, the field-by-field record, the actor and the advisory.
- What happened
- Recent developments
- Reported and circulating
- Data points exposed
- Downstream risk
- Principal risk advisory
- Threat actor
- Background
- Data context
How this breach happened
Raaga, an India-based music streaming and entertainment platform focused on Indian-language audio content, suffered a data breach in approximately mid-December 2025 when threat actors gained unauthorized access to Raaga's systems and exfiltrated a database containing personal information for over 10.2 million user accounts. The data was subsequently posted for sale on an underground hacking forum. The breach was indexed by Have I Been Pwned on January 19, 2026 and covered by Indian and international cybersecurity media in January 2026. Raaga has publicly confirmed the breach but has not detailed the original compromise vector, the specific vulnerability exploited, or post-breach security improvements.
The breach affected approximately 10,225,145 unique user accounts based on records indexed by breach-tracking services. Compromised fields included names, email addresses, gender information, ages and (in some cases) full dates of birth, postcodes for geographic locations, and passwords stored as unsalted MD5 hashes. The unsalted MD5 password storage represents a particularly severe failure mode because MD5 has been recognized as cryptographically broken for over a decade, and the absence of salting allows attackers to use precomputed rainbow tables to rapidly recover the underlying password values. Modern industry standards including bcrypt, scrypt, and Argon2 have been recommended replacements for over a decade.
For affected users, the practical risk profile is severe and long-lasting because the unsalted MD5 password storage means the original password values can be recovered for many users with only modest computational effort. The combination of name, email address, date of birth, gender, and postcode supports targeted phishing and identity-verification bypass attempts at financial institutions, Indian government services where date of birth and contact information may be used for identity confirmation, and other accounts. Inclusion in the dataset confirms a Raaga subscription or account relationship and may support culturally-targeted phishing referencing Indian music, regional language preferences inferred from listening history, or specific Raaga-platform features. Affected users should change any reused passwords immediately on all other accounts, enable two-factor authentication where available, treat unsolicited contact referencing Raaga or related Indian-language services with caution, and remain alert to phishing campaigns referencing real demographic details that may have been included in the stolen dataset.
What has happened since the breach
Raaga has confirmed the December 2025 breach in public statements following the data's appearance on hacking forums in January 2026 and broader industry coverage. The breach has been the subject of significant security-research commentary because of Raaga's use of unsalted MD5 password storage, which has been characterized as a deprecated cryptographic method that the security community abandoned over a decade before the breach. Raaga has not publicly detailed the discovery timeline, the specific vulnerability that enabled the compromise, the timing of user notifications, or post-breach security improvements. The breach is subject to oversight under India's Digital Personal Data Protection Act 2023 (DPDP Act), which carries materially higher potential penalties than earlier Indian data-protection frameworks.
What was reported vs. what is circulating
Reported
- Status
- Not yet researched
Listed in breach catalogues
- Breach date
- Dec 2025
- Volume
- Count not yet verified
- Fields listed
- 7age, date of birth, email address, full name, gender, geographic location, password
The score is built only on what is listed in circulation.
Every exposed field, and how long it stays useful
| Field | Shelf life | In notice | Listed |
|---|---|---|---|
| Age | Fades over a few years | No | Yes |
| Date of Birth | Lasts for years | No | Yes |
| Email Address | Lasts for years | No | Yes |
| Full Name | Lasts for years | No | Yes |
| Gender | Fades over a few years | No | Yes |
| Geographic location | Lasts for years | No | Yes |
| Password | Expires fast | No | Yes |
Shelf life is how long a field stays useful to someone holding it. A password expires fast. A government ID number or a date of birth lasts for years. An address stays useful long after it stops being current.
How attackers can use this data
Primary risks include account takeover, phishing, and interest-based profiling. Listening behavior can also reveal language, culture, and identity signals that improve targeting.
Risks for executives and other high-profile people
A consumer-service breach: contact and account data supports phishing, account takeover and profile enrichment. For a high-profile principal the main risk is credible impersonation and enrichment of existing exposure.
Who is behind this breach
No threat actor has been publicly attributed.
About the company
Raaga is an India-based music streaming and entertainment platform focused on Indian language content including Hindi, Tamil, Telugu, Malayalam, Kannada, Bengali, Punjabi, and other regional Indian language music. Headquartered in India and operating globally at raaga.com, the platform serves a substantial international user base including the Indian diaspora across North America, Europe, the Gulf region, and Southeast Asia. As an account-based music streaming platform, Raaga maintains user account data including names, email addresses, demographic information, geographic location, listening history, subscription billing records, and login credentials tied to audio consumption and recommendation features.
Why the company holds this data
Music-streaming platforms collect user accounts, emails, subscription records, listening history, device identifiers, and engagement data tied to audio consumption and recommendation systems.
About this record
No reported total is on record for this breach. No count has been verified for this breach yet. Figures in older breach catalogues are not shown until they are checked against the data. No score is shown until the circulating field list has been audited. Scores come from the Breach Risk Index, which rates what the exposed fields still let an attacker do, not how large the breach was. Breach records change as evidence does. If you hold a notice, a filing or a dataset observation this page does not reflect, report a correction.