---
title: "Suno outdated-source-code and data incident"
description: "Evidence-backed account of Suno outdated-source-code and data incident, covering what happened, impact, timeline, attack vector, technical details, and primary sources."
incident_type: "Data incident"
status: "active"
last_modified: "2026-08-09"
canonical_url: "https://www.ally.security/incidents/suno-outdated-source-code-data-incident-2025"
markdown_url: "https://www.ally.security/incidents/suno-outdated-source-code-data-incident-2025.md"
stix_url: "https://www.ally.security/incidents/suno-outdated-source-code-data-incident-2025/stix.json"
---

# Suno outdated-source-code and data incident

A Suno-confirmed incident involving outdated source code, with a later HIBP corpus whose personal-data scope is not confirmed by Suno. A verified HIBP corpus associated with Suno; the victim's quoted statement says the incident did not compromise sensitive personal information.

Last modified Aug 9, 2026 · 2 sources

## Summary

- **Environment:** Not publicly identified
- **Operational impact:** No outage or recovery duration quantified
- **Financial impact:** No public cost estimate

## What happened

A [Suno](https://suno.com/)-confirmed incident involving outdated source code, with a later HIBP corpus whose personal-data scope is not confirmed by Suno. [2](#source-2)

## Impact

A verified HIBP corpus associated with Suno; the victim's quoted statement says the incident did not compromise sensitive personal information. [1](#source-1)

A cited record reports 55,282,226 records (Unique email addresses in HIBP's verified corpus; not a Suno-confirmed affected-person, customer, account, purchase, or total-row count; as of 2026-07-20). [1](#source-1)

## Timeline

### November 25, 2025 — Documented event

HIBP's day-level BreachDate; Suno's quoted statement confirms only November 2025, so the exact day remains HIBP-specific. [1](#source-1)

### July 17, 2026 — Public disclosure

Publication date of PC Gamer's report containing Suno's quoted statement; not necessarily Suno's earliest private or public disclosure. [2](#source-2)

### August 9, 2026 — Briefing updated

This briefing was last reviewed and updated on August 9, 2026.

## Threat Group & Attack Vector

The cited public record does not establish a specific initial-access vector, malware family, exploited vulnerability, or ATT\&CK technique.

### Actors

- No threat actor group has been identified in the reviewed public evidence.

### TTPs

- No specific MITRE ATT\&CK technique is currently mapped for this case.

## Response

HIBP marked the Suno incident record verified and not fabricated. A Suno spokesperson said the company determined in November 2025 that it had experienced a limited security incident, quickly contained it, investigated, and found that it primarily involved outdated source code no longer in use. Suno's quoted statement said its investigation verified that no sensitive personal information was compromised. The evidence ledger retains 5 disputed claims with the original citations rather than silently resolving the conflict. No access path, attribution, scale, or recovery detail is inferred beyond the cited claims. [1](#source-1) [2](#source-2)

## Assets

[Download the case-scoped STIX 2.1 bundle](<https://www.ally.security/incidents/suno-outdated-source-code-data-incident-2025/stix.json>)

## Sources

Primary source records used to research this incident.

<a id="source-1"></a>

### Suno breach record

advisory · Have I Been Pwned · Jul 20, 2026

<https://haveibeenpwned.com/api/v3/breach/Suno>

<a id="source-2"></a>

### AI music generator Suno has been hacked, detailing the data scraping of millions of songs from YouTube, Deezer, and Genius

news · PC Gamer · Jul 17, 2026

<https://www.pcgamer.com/software/ai/ai-music-generator-suno-has-been-hacked-detailing-the-data-scraping-of-millions-of-songs-from-youtube-deezer-and-genius/>

<details>
<summary>Evidence ledger</summary>

Review the supporting structured claims.

1. **Resulted In · 100% confidence · current**  
   Suno email, contact, purchase, and partial-card corpus: HIBP marked the Suno breach record verified and not fabricated.
2. **Exposed Data Category · 85% confidence · disputed**  
   Suno email, contact, purchase, and partial-card corpus: Contact information
3. **Resulted In · 95% confidence · current**  
   November 2025 Suno security incident: A Suno spokesperson said the company determined in November 2025 that it had experienced a limited security incident, quickly contained it, investigated, and found that it primarily involved outdated source code no longer in use.
4. **Exposed Record Count · 100% confidence · current**  
   Suno email, contact, purchase, and partial-card corpus: 55,282,226 record
5. **Disclosed At · 100% confidence · current**  
   November 2025 Suno security incident: 2026-07-17
6. **Occurred At · 90% confidence · current**  
   November 2025 Suno security incident: 2025-11-25
7. **Exposed Data Category · 85% confidence · disputed**  
   Suno email, contact, purchase, and partial-card corpus: Names
8. **Affected Organization · 100% confidence · current**  
   November 2025 Suno security incident: Suno, Inc.
9. **Exposed Data Category · 80% confidence · disputed**  
   Suno email, contact, purchase, and partial-card corpus: Payment card information
10. **Resulted In · 75% confidence · disputed**  
   November 2025 Suno security incident: Suno email, contact, purchase, and partial-card corpus
11. **Resulted In · 95% confidence · current**  
   November 2025 Suno security incident: Suno's quoted statement said its investigation verified that no sensitive personal information was compromised.
12. **Exposed Data Category · 80% confidence · disputed**  
   Suno email, contact, purchase, and partial-card corpus: Purchase history

</details>