MyRecon OSINT
Suno
On 25 November 2025, Suno was breached. 55,282,226 accounts were exposed, including email addresses, names, partial credit card data. MyRecon rates it 76/100 — severe. That is roughly everyone in Canada.
What happened
In November 2025, AI music generation tool Suno suffered a data breach that later came to light in July the following year. The data contained over 55M unique email addresses. Phone numbers were also present where they had been used as the sign-up method. Although representing a small portion of the corpus, the breach also included tens of thousands of Stripe records relating to purchases, containing names, physical addresses, purchase amounts and partial credit card data including the card type, expiry date and last 4 digits. The company advised that "Suno does not have access to customers' full credit card numbers in Stripe".
Breach description from Have I Been Pwned, used under a CC BY 4.0 licence.
Who was behind it
No party has been publicly confirmed as responsible, and this page will not name one. Most breaches are never formally attributed: data surfaces on a forum or inside a combined dump long after the intrusion, and the trail back to a specific actor is rarely made public. Where a group has claimed responsibility it is usually named in the account above — that claim is theirs, not a finding of ours.
What was exposed, and why it matters
- Email addressesThe address becomes a confirmed, active target — expect more phishing, better aimed.
- NamesTurns an anonymous address into an identified person, which is what makes targeted phishing possible.
- Partial credit card dataNot enough to spend, but enough to convince a victim that a caller is genuinely from their bank.
- Phone numbersEnables SIM-swap attacks against SMS two-factor codes, and puts the number on scam-call lists indefinitely.
- Physical addressesWhere someone actually lives. Combined with a name this moves the risk off the internet.
- PurchasesWhat was bought and when — detail that makes an impersonation convincing.
What to do if you were in it
- Move two-factor authentication off SMS and onto an authenticator app, which a SIM swap cannot intercept.
- Be sceptical of post and callers who already know your address — knowing it is no longer evidence of anything.
- Expect better-aimed phishing. A message that already knows your name and where you have an account is the whole point of a breach like this.
Questions people ask about this breach
Was my email address in the Suno breach?
Enter it in the box at the top of this page. MyRecon checks it against this breach and every other one on record, and the address is never stored.
What data was leaked in the Suno breach?
email addresses, names, partial credit card data, phone numbers, physical addresses, purchases. Each one is explained above, along with what it means for the person it belongs to.
When did it happen, and when did it become public?
The breach is dated 25 November 2025. It was published to Have I Been Pwned on 20 July 2026, a gap of 238 days during which the data was already out.
Is the Suno breach real?
Yes. Have I Been Pwned lists it as verified, meaning the data was checked against the source rather than taken on trust.
How many people were affected?
55,282,226 accounts. That is roughly everyone in Canada. That is accounts rather than people — one person often has several.
Read next
Also in the archive
Severity is scored by MyRecon from the number of accounts, the sensitivity of the specific fields exposed, and whether the breach is confirmed — not by a language model. The description above is quoted from Have I Been Pwned; the analysis around it is ours.