People should be using email alias. 1 unique alias per 1 uniques service and websites for proper segregation. If any of the unique alias leaked or getting spammed you'd know where the source is and blocking that specific alias would limit the breach. Theres simplelogin.io, addy.io, firefox relay, apple hide-my-email, custom domain catchall etc for that.
IMO use email providers that have that built in. Because if your alias provider goes down, you’re fucked. And considering it’s a much less stable business than an email provider, it’s more likely.<p>If Gmail goes down in 20 years, it will be a major occurrence. If mailgoforward.fart goes down, you’re screwed.<p>The advice is, as always, use a second mail address for “sensitive” providers. Use a password manager and two factor for everything. Ideally one that integrates into your phone and browser.<p>For traceability, most providers support a + alias syntax now. Ie foobar+baxservice@provider.com
I don't get why + addresses always come up in this. They're machine-undoable by design.<p>Using randomized relay addresses instead gives you an immensely higher confidence that when a given contact address starts getting spam, it is misuse stemming from a specific entity. Especially if you rotate it at a fixed time interval, cause then you can even establish a starting timeframe.<p>Still not perfect but it can never really be, and not even out of email's fault. As long as DNS and IP addressing rule the world, there's only so much one can do. It's a secret handling problem at its core.
I went through and deleted a bunch of accounts a while ago, SoundCloud being one of them. It looks like I don't show up in the breach. It's nice to know SoundCloud actually deleted my data, I'm never totally sure what happens on the backend.
I still have two active accounts and neither of those were in the breach of the 20% of accounts.
They still seem to use past email addresses for marketing communications, despite the email address on file having been changed months ago. They definitely still keep old data around and fail to sync data between vendors. Whether that's indicative of their data deletion policies remains to be seen, but to me the lack of care for using past data for active accounts doesn't paint them in a very good light.
Only 20% of accounts were breached, so that's an optimistic conclusion.
In theory, it's a legal requirement based on GDPR and CCPA as well as many other new digital rights laws across Europe and many states in the USA. SoundCloud is probably big enough to do that correctly otherwise e.g. the GDPR penalty is a highish percentage of the company's total revenue which gives the laws a good amount of "teeth".
For some services, like Anthropic/Claude's stubborn refusal to let you remove your payment method, deleting isn't even an option.
I ran into this with Sony. The website said to call, so I did. After 45 minutes on hold the guy just hung up on me saying he couldn’t help, without even really listening to me.<p>For a company that’s been hacked as many times as Sony, I find this to be pretty pathetic.
"The data involved consisted only of email addresses and information already visible on public SoundCloud profiles".<p>So they've scraped public data. Why care?
Hackers stole information of 29.8M accounts (~20% of users). SoundCloud is downplaying the data beyond email address as "publicly available", but the data wasn't scraped. "Profile statistics" aren't public either. Their main response[0], seems to focus on passwords and payment details being the only risky data. They even imply email addresses are public.<p>> no sensitive data was taken in the incident.The data involved consisted only of email addresses and information already visible on public SoundCloud profiles (not financial or password data)<p>[0]: <a href="https://soundcloud.com/playbook-articles/protecting-our-users-and-our-service" rel="nofollow">https://soundcloud.com/playbook-articles/protecting-our-user...</a>
Maybe the two public data points weren't connected before?<p>I don't use SoundCloud, but if profiles didn't have contact information like Email Address on them then it could be meaningful to now connect those two dots.<p>Like, 'Hey look, Person A, who is known to use email address X, kept Lost Prophets as one of their liked artists even after 2013!'
Yeah or this: <a href="https://news.ycombinator.com/item?id=26386418">https://news.ycombinator.com/item?id=26386418</a><p>SoundCloud is a weird place, people in entertainment have certain strong incentives. They figured out who I am, figured out all the email addresses I have, jacked the account attached to my SoundCloud, stole my account. I still to this day, don't know how they pwned my email (tfa was on but it didn't trigger suspicious activity it let them login without triggering it, no clue how they got the password either and the password is secure enough that it's too hard to brute force, and it's not in a pwned db). Based on what was in my soundcloud inbox when I got access again, someone paid a fair amount to have this done... and now I have to go change my email <i>again</i> I suppose.
But, why care? (Yes, we can “care” that there was a leak - but… <i>why worry?</i> what new risk exists today that didn’t yesterday?)<p>The data in the leak (other than follower count, etc) was already available for purchase from Zoominfo, 8sense, or a variety of other data brokers or other legal marketplaces for PII.<p>I suppose the risk now is that the data is freely available and no longer behind a data broker’s paywall?
I'm confused, where were scrapers/data brokers/Zoominfo etc. were getting email addresses for SoundCloud accounts?
Isn't that a huge GDPR violation?
You are 100% correct based on article. Not good that you're gray, and your parent of "who cares it was already available and scraped" is the top comment.
> the impacted data included 30M unique email addresses, names, usernames, avatars, follower and following counts and, in some cases, the user’s country
Importantly, 20% of the total userbase it seems:<p>> In December 2025, SoundCloud announced it had discovered unauthorised activity on its platform. The incident allowed an attacker to map publicly available SoundCloud profile data to email addresses for approximately 20% of its users. The impacted data included 30M unique email addresses, names, usernames, avatars, follower and following counts and, in some cases, the user’s country.<p>That's from the haveibeenpwned email which I received because of course I'm part of that 20%.<p>Remember to have unique passwords for each website kids, ideally with a password manager.
Whilst thats important advice, as far as I can tell it wouldnt help here as no passwords are breached. I had a few of our domain users on this report and as far as I can tell theres nothing actionable.
Also, never give out a direct email address, always an alias.
If I’m understanding correctly, it sounds like, aside from the email addresses, all the data leaked was already publicly available on users’ SoundCloud profiles. The only novel aspect is linking that public data to the accounts’ email addresses.
SoundCloud is the worst company, so hostile to former paying users! I am a hobbyist songwriter and have posted my rough mixes (Apple's Music Memo app which adds drum and bass automagically with two clicks & then mix it in Garage Band) on my SoundCloud for more then ten years. I signed up for their Artist Pro account and was a member for of such consistently for a few years at $17 a month. Once you cancel they then hold all your music hostage by hiding it and later threat to delete it. Horrid!
A former paying user is not a customer. If you don't pay, why should you receive service? I buy a pizza at this pizza shop every week, but I still don't get free ones.<p>SoundCloud is European, so most of the dark patterns used by American companies to offer "free" service are not available to them, and they are required by law to actually delete data instead of pretending to delete it.
The difference between Artist vs Pro is three hours vs unlimited uploaded music.<p>So if you had over three hours uploaded, it seems reasonable for them to restrict the service. If you had <= three, then it would a problem.
SoundCloud used to be good prior to the redesign.<p>Recently I decided to evaluate it for serious use and start posting there again, only until their new uploader told me I need to switch to a paid plan, even though I triple-checked I was well within free limits and under my old now unused username I uploaded a lot more (mostly of experimental things I am not that proud of anymore).<p>It looks like their microservices architecture is in chaos and some system overrides the limits outlined in the docs with stricter ones. How can I be sure they respect the new limits once I do pay, instead of upselling me the next plan in line?<p>Adding to that things like the general jankiness or the never-ending spam from “get more fake listeners for $$$” accounts (which seem to be in an obvious symbiosis with the platform, boosting the numbers for optics), the last year’s ambiguous change in ToS allowing them to train ML systems on your work, it was enough for me to drop it. Thankfully, it was a trial run and I did not publish any pending releases.<p>If you still publish on SoundCloud, and you do original music (as opposed to publishing, say, DJ sets, where dealing with IP is problematic), ask yourself whether it is timr to grow up and do proper publishing!
This sounds like a classic consistency vs latency trade-off. Enforcing strict quotas across distributed services usually requires coordination that kills performance. They likely rely on asynchronous counters that drift, meaning the frontend check passes but the backend reconciliation fails later. It is surprisingly hard to solve this without making the uploader feel sluggish.
You can export your entire profile using yt-dlp. Of course you have to do it, when you are still a paying customer.
Do this regularly, like youtube soundclownd ‘silent’ deletes favorites and also blocks songs based on your vpn/geo location. I lost so much music… so i need to resort to scraping. Simple solution: make the song unavailable but please just keep the entry (name-title) in your fav. list.
Why would someone that writes their own songs, mixes in GarageBand, uploads to a 3rd party website need to use yt-dlp to get back the files that they themselves made?<p>Yes, I'm intentionally victim blaming here. The <i>victim</i> is complaining about a 3rd party site deleting files. Who cares? Why would you have as your only source of your files the copies stored by the 3rd party?
You get a point there, but export is mostly about metadata, eg images and description.<p>Data loss happens too. Soundcloud may be your only source of your own tracks.
Date of publication (copyright) is important to a songwriter. Soundcloud im sure knows this! Probably should have said this from the top!
Not only that, the victim is complaining about a paid file storage company deleting the files when the victim stops paying
You mean you never kept your originals but just uploaded and deleted the masters?
that just sounds like customer not paying for service not getting the service
The service is freemium, so they had a limited account. Decided to pay for a premium account. And apparently can’t downgrade and get back what they once had.
I'm just guessing, but this:<p>> and have posted my rough mixes [...] on my SoundCloud for more then ten years<p>...easily implies >3h of uploads, which is over the free plan limit. If you're over that limit and stop paying, yes, it makes perfect sense that they'd threaten with deletion of some of your existing uploads.
They first hide your songs and as time goes on they start threaten to delete your songs if you dont pay
I'd pay for Soundcloud, but not sure what I'd get for over free version. It costs more than Apple Music and offering offline nowadays is lol feature.
Are there any alternatives?
A lot of people use apps like this lately: <a href="https://untitled.stream/" rel="nofollow">https://untitled.stream/</a>, <a href="https://gatefolded.com/" rel="nofollow">https://gatefolded.com/</a>, <a href="https://samply.app/" rel="nofollow">https://samply.app/</a>
Isn't everyone on YouTube or Bandcamp now for this use case?
A lot of "rap gods" are about to be exposed as "Kevin" from suburbia.
Thankfully the only artist I listen to on there has been known as Bryce from the suberbs for two decades:<p><a href="https://soundcloud.com/ytcracker" rel="nofollow">https://soundcloud.com/ytcracker</a>
Lil B is probably fine, but he is the biggest name I recall coming out of SoundCloud. He blew up all over the 2010s, he was the Kanye of Cloudrap too because he took dressing styles and changed it all up similar to Kanye.
Shout out to lil b and those parties at Berkeley he would perform at in ‘12, ‘13.<p>Those were the golden sound cloud years.
There's a few big names: Post Malone, Billie Eilish, Lil Nas X, Khalid, Bad Bunny
This Kevin was still quite impressive<p><a href="https://en.wikipedia.org/wiki/Kevin_Mitnick" rel="nofollow">https://en.wikipedia.org/wiki/Kevin_Mitnick</a>
An email–only breach seems to cheapen the value of HIBP. It's not telling me if my password was leaked.
So I guess I should watch out for scams being sent to "soundcloud@" on a personal domain. Oh no, how will I distinguish them from my legitimate banking email???
Clever spammers (there are some!) see the presence of company@<domain> and assume the user will have similar emails for other accounts, so it might be worth trying ebays scams to ebay@<domain> or banking scams to chase@<domain> or boa@<domain>. Sending is cheap so why not, you're not trying to fool everyone, only a few.<p>I use a unique string per company but it's not guessable in advance, but it's obvious when looking at it and squinting a bit, for example (and these are not the exact ones I use): sundclod@<domain> or ebuy@<domain> or amzoon@<domain><p>Sure I have to remember them but it's easy for me to check and my password manager is filling them in for me 99.99% of the time.<p>I can filter on those emails instead, and I also know that anything coming to soundcloud@<domain> or ebay@<domain> or amazon@<domain> is definitely spam as I've never used those addresses myself.<p>If sundclod@<domain> appears in a leak I can (hopefully) change my account email at Soundcloud to sondclud@<domain> and then confine sundclod@<domain> to /dev/null
We are the minority of users that had enough foresight to do this. I'd bet that _most_ people on this breach don't even know about the plus/dot trick with gmail (and I am sure other providers, too).
Oh nice. Maybe I can finally recover (and finally shut down) my old account I accidentally locked myself out of.
making mountains out of mole hills. this type of panic is really common in the infosec world.
Kinda sad to see a "Recommended Actions", with only sponsors, with ad copy that would be understood by HN readers but not our non-technical friends. (i.e. a simple "Nothing. No passwords have been leaked yet, only metadata" in this case)
Glad that I removed my SoundCloud account right on time.<p>I think it’s only a matter of time before a service gets breached.<p>It's best to use unique random username, email, and password for every online account.
Also, providing only the bare minimum of data and faking as much as possible is helpful in cases of data breaches.
all this leaked data pretty much used for one objective now: stealing crypto
By aggregating breach data by email, this tool inadvertently exposes users's full web history, including sensitive sites like crypto/adult/dating platforms, to anyone who knows their address<p>Fun
From the FAQ [1]:<p>What is a "sensitive breach"?<p>HIBP enables you to discover if your account was exposed in most of the data breaches by directly searching the system. However, certain breaches are particularly sensitive in that someone's presence in the breach may adversely impact them if others are able to find that they were a member of the site. These breaches are classed as "sensitive" and may not be publicly searched.<p>A sensitive data breach can only be searched by the verified owner of the email address being searched for. This is done by signing in to the dashboard which involves verifying you can receive an email to the entered address. Once signed in, all breaches (including sensitive ones) are visible in the "Breaches" section under "Personal".<p>There are presently 82 sensitive breaches in the system including Adult FriendFinder (2015), Adult FriendFinder (2016), Adult-FanFiction.Org, Ashley Madison, Beautiful People, Bestialitysextaboo, Brazzers, BudTrader, Carding Mafia (December 2021), Carding Mafia (March 2021), Catwatchful, CityJerks, Cocospy, Color Dating, CrimeAgency vBulletin Hacks, CTARS, CyberServe, Date Hot Brunettes, DC Health Link, Doxbin and 62 more.<p>[1] <a href="https://haveibeenpwned.com/FAQs#SensitiveBreach" rel="nofollow">https://haveibeenpwned.com/FAQs#SensitiveBreach</a>
You don't get to gatekeep what counts as "sensitive", all of my privacy is non-negotiable
> Bestialitysextaboo<p>I laughed pretty hard