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.
Eight months passed between the breach date on this record and the point at which it came to light. That gap is the most useful thing on the page. Everyone in the file spent most of a year with no reason to change anything, while the data was already out, which is why "there is no evidence of misuse" is a statement about what the company can see, not about what has happened.
The second detail worth noticing is the shape of the exposure. Fifty-five million email addresses with names and phone numbers is a contact list. The tens of thousands of payment records inside it are a different category entirely: a much smaller group, exposed far more seriously, buried inside a number so large that the distinction disappears from most coverage.
If you only ever generated a few tracks and never paid, your realistic risk is targeted phishing that references a service you actually used. If you bought anything, you are in the smaller set, check the card statement for that period specifically, and treat any message about a subscription or refund as unverified until you have opened the account yourself.
The story behind the breach
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.
How did it happen?
The published account does not explain the exact way the data was obtained.
What was the motive?
The published account does not establish the motive. We cannot tell what the attackers intended from the exposed data alone.
Reported demands or attempts to sell data describe what happened, rather than prove every attacker's intention.
What was the outcome?
55,282,226 accounts are listed in this breach. This is a count of accounts, not necessarily individual people.
The reported exposed data includes Email addresses, Names, Partial credit card data, Phone numbers, Physical addresses, Purchases.
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?
Use the email box on this page. The result applies only to this incident. If the provider does not cover this breach, we say so. A missing match does not prove you were unaffected.
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
Case Files: how the landmark breaches actually happened →
Three kinds of content appear on this page and they are kept apart deliberately. The breach description is quoted from Have I Been Pwned under its licence. The severity score, the field-by-field explanation and the advice are computed from the record itself, every sentence derives from a number or a flag in it, which is what stops the analysis drifting from the evidence. Anything under the "MyRecon's take" byline is editorial: our reading of this breach, presented as opinion rather than as a finding.