SoundCloud experienced a cyberattack that resulted in unauthorized access to an ancillary service dashboard, leading to the exposure of limited user data. The company confirmed that the attackers accessed email addresses and information already visible on public SoundCloud profiles, affecting approximately 20% of its user base—estimated at around 26 to 28 million accounts. SoundCloud stated that no sensitive data, such as financial or password information, was compromised. In response, the company activated its incident response protocols, engaged third-party cybersecurity experts, and implemented enhanced monitoring, threat detection, and access control measures.
Following the breach, SoundCloud faced multiple denial-of-service attacks that temporarily disrupted the platform's web availability. Additionally, a configuration change made during the incident response process inadvertently disrupted VPN access for users, resulting in widespread reports of 403 "forbidden" errors when attempting to connect via VPN. SoundCloud has since contained the unauthorized access and is working to restore full service, including VPN connectivity, while continuing to audit and reinforce its security posture.

Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
7 events from the most recent confirmed update back to the earliest known activity.
In the wake of the breach, SoundCloud urged users to remain alert for phishing attempts and to improve account security, including changing passwords and enabling multi-factor or two-factor authentication. These recommendations were issued because exposed email and profile data could support social engineering attacks.
Reports published on December 16, 2025 said the ShinyHunters extortion group was believed to be behind the SoundCloud breach and was allegedly attempting to extort the company by threatening to leak the stolen data. Some reports noted it was unclear whether the same actor also conducted the DoS attacks.
By December 15-16, 2025, SoundCloud confirmed that roughly 20% of its users—reported as about 26 to 28 million accounts—were affected by the data theft. The company stated that only email addresses and public profile data were exposed, not passwords or payment information.
Following containment of the breach, SoundCloud was hit by multiple DoS/DDoS attacks that caused temporary outages on its web platform. Mobile and API services reportedly remained available during these disruptions.
As SoundCloud implemented configuration and security changes following the breach, some users experienced temporary VPN-related connectivity problems. The company said it was not intentionally blocking VPNs and was working to resolve the access issues.
After detecting the intrusion, SoundCloud activated incident response procedures, engaged third-party cybersecurity experts, blocked unauthorized access, and reviewed monitoring and access controls. The company said it believed the attackers no longer had access to its systems.
In December 2025, attackers gained unauthorized access to an internal or ancillary service dashboard at SoundCloud and exfiltrated a user database. The stolen data was limited to email addresses and publicly visible profile information, with no passwords or financial data accessed.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
6 references tracked. Mallory keeps watching after this page renders.
techrepublic.com
Open sourcego.theregister.com
Open sourcecybersecuritynews.com
Open sourcehelpnetsecurity.com
Open sourcehackread.com
Open sourcebleepingcomputer.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.