Hacker Leaks Suno Source Code Exposing Massive Scraping of 2 Million YouTube Music Tracks and Customer Data Breach
A hacker operating under the pseudonym ellie.191 has leaked the internal source code of Suno, one of the largest AI-powered music generation platforms, to the investigative outlet 404 Media. The disclosure reveals how the company systematically scraped millions of copyrighted tracks and podcasts to train its generative models.
The leaked materials, believed to originate from 2023 and 2024, contain detailed instructions for downloading content and precise records of dataset sizes. According to the code, Suno obtained more than 2 million music fragments from YouTube Music alone. Additional sources listed in the files include Pond5, Jamendo, Freesound, the International Music Score Library Project, and MuseScore.
One dataset comprised over 152,000 hours of labeled audio from YouTube Music, while another collection from the same platform added 114,000 hours. Approximately 62,000 hours came from Pond5 and more than 12,000 hours from Deezer. Separate scripts were designed to locate karaoke-style versions of songs on YouTube to extract isolated vocals.
To facilitate large-scale downloads, Suno relied on proxy infrastructure provided by Bright Data. Another tool identified 420,000 podcasts and prepared nearly 1 million hours of recordings for ingestion.
The publication corroborates allegations previously made by the Recording Industry Association of America, which accused Suno of bypassing YouTube’s technical protections to copy protected works. Although Suno has publicly stated it trained on tens of millions of publicly available recordings under a fair-use rationale, rights holders continue to challenge this position in court.
In addition to the training data, the hacker claims to have obtained records belonging to hundreds of thousands of Suno customers, including email addresses, phone numbers, and partial payment information processed through Stripe. Several affected users have already verified to 404 Media that the exposed phone numbers match their accounts and that they never received breach notifications.
Suno responded that it detected a limited intrusion in November 2025 and quickly contained it. The company maintains that only outdated source code was accessed and denies that any sensitive personal or full payment card data was exposed. The hacker stated that access was achieved through an employee account infected by the Shai-Hulud worm, which harvested GitHub and cloud-service credentials, and that the operation was conducted out of general curiosity rather than targeted malice.
Related articles
OpenCode Reports Possible Exposure of Third-Party API Keys After Legacy System Breach
OpenCode disclosed that an attacker accessed a legacy system on October 16, potentially exposing API keys from external providers that users had stored in the Console. The incident affected only 1.4 percent of Console users, and the targeted system was already undergoing decommissioning. The company described the exposure as possible rather than confirmed and provided no details on the attack vector, duration, or number of keys involved. Some affected users reported unauthorized charges on their provider accounts. OpenCode stated that the incident was limited to keys stored in the Console and did not impact keys saved locally in its command-line or desktop applications. The firm notified impacted users by email on October 17 and is working with Anthropic, OpenAI, and Google. It recommended revoking and rotating exposed keys directly with each provider.
Moscow Court Places Dodo Pizza Cyberattack Suspect Denis Fridman Under House Arrest Until 2026
The Tverskoy District Court of Moscow has ordered Denis Fridman to remain under house arrest until December 8, 2026, in connection with a cyberattack on Dodo Pizza that occurred in late September. Fridman faces charges under paragraphs a and v of part 3 of Article 272.1 of the Russian Criminal Code, which covers the illegal circulation of computer information containing personal data. Investigators detained three of the four suspects after Fridman failed to mask his real IP address while accessing the stolen dataset. The breach lasted two days, but Dodo Pizza quickly blocked access and confirmed that payment details were not compromised because the company does not store them. Authorities notified Roskomnadzor of the incident and implemented measures to forcibly terminate active user sessions where necessary. House arrest remains a preventive measure, and Fridman’s guilt has not yet been established by the court.
Yandex Disk Data Center Incidents Leave Photos and Videos Inaccessible, Custom Recovery Tool Emerges
Following incidents at Yandex data centers in Sasovo and Vladimir, large numbers of photos and videos stored on Yandex Disk became unavailable for normal download. The company attributed the restrictions to load reduction, yet analysis indicates permanent loss of certain data clusters with no confirmed backups. Photos remain partially recoverable through lower-resolution S3 copies such as XXXL and XXL, while videos suffer from missing byte ranges that produce truncated or corrupted files. A researcher developed a specialized tool using mitmproxy to intercept browser requests and download available file variants in parallel streams. The utility also attempts block-by-block video retrieval to salvage whatever segments remain accessible. Users are warned that continued use of the tool may violate service terms and risk account suspension. The developer advises downloading data immediately rather than waiting for potential further degradation.
AT&T to Pay $177 Million to Settle Two 2024 Customer Data Breach Class Actions
AT&T has agreed to pay a total of $177 million to resolve two separate class-action lawsuits stemming from major customer data leaks that occurred in 2024. The settlement, approved on October 2 by Judge Sidney Fitzwater in the Northern District of Texas, allocates $149 million to the first breach and $28 million to the second, covering compensation, attorney fees, and administrative costs. The first incident, disclosed on March 30, 2024, exposed personal information of 73 million individuals, including names, addresses, phone numbers, dates of birth, account passwords, billing numbers, and Social Security numbers for some victims, with records dating from 2019 or earlier found on the dark web. The second breach originated from unauthorized access to AT&T’s Snowflake cloud environment between April 14 and 25, 2024, affecting nearly all mobile customers and revealing call metadata such as phone numbers, interaction counts, durations, and cell tower identifiers from May to October 2022 plus January 2023. No evidence of direct system intrusion was found in the first case, and the second exposure did not include Social Security numbers or call content. Individual claimants can receive up to $5,000 or $2,500 respectively for documented losses, with the claims deadline set for December 18, 2025. AT&T settled without admitting any wrongdoing or liability.