Someone Released Music Under My Artist Name: What to Do in 2026
On 10 September 2026 a track called "Riding High" appeared on the verified Spotify page of Lathe of Heaven, a Brooklyn punk band who did not write it, play on it or release it. A journalist had generated it and delivered it under their name to prove how cheap the route is. If **someone released music under my artist name** is the sentence you just typed into Google, the key takeaways below are the short version: there are four different things that could have happened to you, they have four different owners, and Spotify's own support page assumes the one that is least likely to be true in 2026. We read both of the support documents Google ranks for this, Spotify's own policy announcements, and the reporting that broke the case, at source, on 27 September 2026. This is a research page, not legal advice, and the routes described are the US ones.
- Spotify named this exact tactic in its own newsroom on 25 September 2025 — "uploaders fraudulently deliver music (AI-generated or otherwise) to another artist's profile" — a full year before a reporter reproduced it end to end.
- The two pages Google ranks for this problem both describe it as an accidental metadata mix-up. The documented 2026 cases are deliberate, and the fix route is the same form either way.
- Spotify told 404 Media that "profiles that aren't actively managed can be especially vulnerable." Claiming your profile is the single preventative measure the platform itself points at.
- The uploader collects the royalties on every stream until the release is pulled. Neither support document says anything about getting that money back, and we are not going to invent a procedure that does not exist.
- The cheapest defence is asking your distributor to deliver with your specified artist ID — the one preventative Spotify names by name — and it costs nothing.
Someone released music under my artist name used to describe a filing error. In 2026 it more often describes a delivery that somebody made on purpose — and both land in the same inbox, on the same form.
On 10 September 2026 a track called "Riding High" went live on the verified Spotify page of Lathe of Heaven, a Brooklyn punk band. It sounded nothing like them because it was generated in Udio by Emanuel Maiberg of 404 Media, who published the whole thing on 17 September to show how little the route costs: a $3.75-a-month distributor subscription and a few minutes. Within a day the same release had reached Apple Music, Tidal and Amazon Music.
The stakes for you are money and credit, in that order. The uploader is paid for every stream until the release comes down, and your page carries a song you did not make while it happens. But the first decision is not which form to fill in — it is working out which of four different things has actually happened, because only one of them is the accident that the two pages Google ranks for this both assume.
Below: the diagnosis, the claim-and-lock step, the three takedown routes with what each actually fixes, what is knowable about the royalties, and the part written for the person most likely to cause this by accident — an AI-music maker typing into a free-text box.
First, work out which of four things happened
Four distinct situations produce the same symptom. They have different owners, different routes and different answers to "does anyone owe me money", so guessing wrong costs you days.
| What happened | What you would see | Who can fix it | Does anyone owe you money |
|---|---|---|---|
| Accidental metadata merge — another act with a similar name, delivered without an artist ID | A release in a style not yours, often a different genre entirely, by a real act with a near-identical name | Spotify, via the content mismatch form; permanently, your distributor | No. Nobody did anything wrong |
| Deliberate delivery under your exact name — the 2026 case | A release you have never heard of, frequently AI-generated, credited to you, earning | Spotify plus your distributor; the uploader's distributor is the choke point | Yes — the uploader is collecting your page's streams |
| Your own distributor delivered without your artist ID | Your new single sitting on a second, empty profile instead of your real one | Your distributor, by redelivering with the ID | No, but your streams are split across two pages |
| Catalogue split across two profiles | Half your releases on one page, half on another, both plausibly you | Spotify, by merging on request | No. Your own royalties, wrong shopfront |
The reason this table has to come first: Spotify's support page for the symptom is titled "Music mixed up with another artist", and it is written end to end for row one. It talks about metadata problems and best practices. It never mentions AI, impersonation or anyone doing this on purpose. Ditto Music's equivalent help page takes the same line. If you are in row two, the route those pages give you is still the right one — but their framing will tell you this was nobody's fault, and in 2026 that is frequently untrue.
How the loophole works, and why we are not printing the steps
The shape is simple enough to describe in one paragraph. The artist-name field on a distributor's upload form is free text. Distributors match a delivery to an existing profile on that string, the uploader self-certifies that they are entitled to it, and the platforms accept the match. There is no identity check anywhere in that chain, which is why a $3.75 subscription was enough.
That is as far as we will go. The offensive half of the 404 Media piece is a live abuse route that people are currently running at scale against working musicians, and restating it in operable order on a site read by AI-music makers would be indefensible. The defensive half is the useful half, and it is the rest of this page.
What is worth knowing is how long this has been visible in public:
| Date | What happened | Source |
|---|---|---|
| July 2025 | A generated country song, "Together", appears on the Spotify page of Blaze Foley, murdered in 1989. Spotify removes it "for violating our Deceptive Content policy" and names SoundOn as the distributor. A second track lands on Guy Clark's page | The FADER, 22 July 2025 |
| 25 September 2025 | Spotify announces its AI safeguards package and describes the tactic itself: "uploaders fraudulently deliver music (AI-generated or otherwise) to another artist's profile" | Spotify Newsroom |
| 10 September 2026 | "Riding High" goes live on Lathe of Heaven's verified page and reaches three other stores | 404 Media, 17 September 2026 |
| September 2026 | Spotify says it is "working directly with distributors to stop bad submissions at the source" and is building a system requiring artists to verify new tracks are theirs | Engadget, Plagiarism Today |
Read that sequence twice. Spotify's own September 2025 announcement named this delivery tactic in writing, and the impersonation policy it shipped alongside covers vocal impersonation — AI voice clones, allowed only where the impersonated artist authorised it. The name field was a separate matter then and it was still open twelve months later. The verification system now being described is the fix, and it does not exist yet.
How to claim your artist profile on Spotify, and lock it down
This is the part with the highest return, and it takes an evening. Spotify told 404 Media that "profiles that aren't actively managed can be especially vulnerable" — the most actionable sentence anyone has published on the subject, and it exists in a news article rather than in Spotify's documentation.
- Claim the profile. If you have a release live, a profile already exists whether or not you have ever logged in. Spotify's support flow is the "Get access" route into Spotify for Artists; our Spotify for Artists guide walks the whole dashboard.
- Do the same on every store you distribute to. One delivery reaches all of them, so one unclaimed page is the gap.
- Ask your distributor to deliver with your specified artist ID. This is the one preventative Spotify names by name. Its own page says its preferred and recommended providers — CD Baby, DistroKid, EmuBands, iGroove, Record Union and Vydia — "let you deliver music with a specified artist ID to help prevent your music getting mixed up in the future." A name string can be typed by anyone; an ID cannot.
- Set a monthly reminder to look at your own pages. Dormant is the risk factor. Twenty seconds a month removes you from the category.
| Platform | Where you claim it | Fast lane |
|---|---|---|
| Spotify | Spotify for Artists, via the access request in its support flow | Several distributors grant access directly |
| Apple Music | Apple Music for Artists — claim your artist page | Sign in with a social or distributor account for faster verification; you must hold the primary artist role on the album |
| Amazon Music | Amazon Music for Artists | Instant access for CD Baby, DistroKid and TuneCore artists authenticating with the distributor login |
| Tidal | Tidal for Artists (artists.tidal.com) |
Request-and-verify; distributor-linked access on some plans |
Every platform above requires at least one live release before a profile exists to claim. If you have not released yet, the claim step is the first thing to do after your debut goes live — not months later.
Getting the release taken down: three routes, and only one form
Three routes exist and they are not interchangeable. The mistake we see is people filing an infringement claim for a release that is not their music, which is the wrong form and starts the clock again.
| Route | Who it is for | What it fixes | Realistic expectation |
|---|---|---|---|
| Content mismatch form | You, with Spotify for Artists access | Removes the release from your profile and corrects the credit | Spotify says "usually within a few days" — its own estimate, not a measured one |
| Your distributor | Anyone; faster if the uploader used the same distributor | Can pull a release at source, which clears every store at once | Hours to days, depending on support queue |
| Infringement claim | Only if the audio is your recording, taken and re-uploaded | Removes an infringing copy | A legal process, not a metadata correction |
The content mismatch form is the route for the case on this page, and note its precondition: you need Spotify for Artists access before you can file, which is why claiming comes first. If a fan spotted this and you have no access yet, start the claim and the form in the same sitting.
Spotify has a separate page for music that impersonates another artist's voice — relevant if the track is a voice clone of you, not merely credited to you. Two different harms, two different documents.
Who keeps the royalties
Here is what is knowable, stated plainly, with nothing added.
The uploader is paid. Royalties follow the delivery rather than the profile, so whoever delivered the release receives the streaming revenue for as long as it is live. Plagiarism Today put it exactly: the song sat on Lathe of Heaven's profile, "but he would get the royalties for the streams."
Recovery is not a documented process. Neither Spotify's support page nor Ditto's says a word about money already paid out, and we are not going to sketch a procedure that no platform publishes. What you control is how many days the release stays up, which is why diagnosis and the right form matter more than anything else on this page.
It is worth being honest about the scale, too. For most independent releases the royalties at stake over a few days are small — what streaming actually pays per stream does not suddenly improve because the wrong person is collecting it. The larger cost is a catalogue you do not control, on a page listeners judge you by. That is also the argument for having somewhere to sell that cannot be edited by a stranger typing into a text field: paid sync placements are where the real money in this niche is, and a direct storefront on the same footing keeps both the relationship and the revenue where nobody can merge them into somebody else's profile. Neither route depends on algorithmic discovery, which is the wall most artists here are already up against.
If you are the one uploading AI music, read this
Most of our readers are making tracks, not managing a hijacked page, so this section is for you, and it is the half no consumer-facing page will write.
The artist-name field is not a search box. It is the string your entire release is matched on. Typing a name that already belongs to someone — or close enough to it — is how your single ends up on a stranger's page and how you end up in a rights dispute you did not intend to start. Before you deliver:
- Search the exact name on Spotify, Apple Music and Bandcamp. If anything comes back, pick another name.
- Check that the name is not a near-match: one word apart, a spacing variant, or the same name with "official" appended all merge in practice.
- Never type an existing act's name to ride their traffic. It is the tactic in the 404 Media piece, it is being actively hunted now, and the distributor account it burns is yours.
- Once you have chosen, give every distributor the same spelling, and ask them to deliver with your artist ID from release one.
If your own track has been lifted and re-uploaded by somebody else — the mirror image of this page — the route is different and we walk it in someone re-uploaded my AI track.
Dead artists, estates and dormant catalogues
The most documented cases are the ones nobody is watching. Blaze Foley was murdered in 1989; a generated country song appeared under his name in July 2025, and Craig McDonald of Lost Art Records, who runs the distribution for Foley's catalogue, told reporters the track was uploaded without permission and was nowhere near Foley's style. Guy Clark, who died in 2016, got the same treatment. Engadget's reporting on the 2026 case notes dead artists among the recurring targets.
An estate or legacy label has the same routes as anyone else, with one extra obstacle: nobody may have ever claimed the pages. If you administer a catalogue for an artist who has died or stopped releasing, the work is exactly the four steps above, done once — claim each page, name a person responsible for looking at them, and get the artist ID into every delivery. A profile with a human attached is a profile that gets checked, and the vulnerability Spotify described is the absence of one.
What this has to do with the DistroKid lawsuit
You may have seen this discussed alongside Universal's case against DistroKid. The connection is real but specific.
UMG's complaint alleges that the distributor had recording-level knowledge of infringing material and kept distributing it; DistroKid has not had its defence tested in public, and nothing has been proved. The loophole on this page is the mechanism that makes an allegation like that concrete: if a delivery pipeline accepts a free-text artist name and a self-certification, then what reaches the stores is whatever the uploader typed, and the distributor is the only party positioned to check. Our page on the UMG v DistroKid lawsuit covers the filing itself. Whether Spotify's promised verification step arrives before the courts get there is the open question — and either way, claiming your pages is the part you can do this week.
Questions readers ask.
Partly. Claim your profile on every platform you distribute to, so the pages are actively managed rather than dormant, and ask your distributor to deliver every release with your specified artist ID rather than matching on the name string. Spotify names both of those itself. Neither closes the loophole — the free-text field is on the distributor's side, not yours — but both remove you from the category Spotify describes as especially vulnerable.
No, and the Lathe of Heaven case is the proof: the track landed on a verified page. Verification tells listeners the profile is genuinely the artist's; it does not gate what gets delivered into it. Active management is what matters, not the badge.
The uploader does. Royalties follow the delivery, not the profile, so whoever delivered the release is the one being paid until it is removed. Recovering money already paid out is a matter between the platform and the distributor and neither Spotify's nor Ditto's help page addresses it, so treat speed of removal as the thing you actually control.
That is a different problem with a different fix — two real artists whose catalogues keep merging on a name string. The content mismatch form is the right route, and the durable fix is having each distributor deliver to a specified artist ID so the match is made on the identifier instead of the text. Nobody is at fault and nobody owes anybody money.
Yes — artist profiles on streaming services are generated from delivered releases, not signed up for, so claiming a page that already exists is the normal path rather than the exception. Spotify, Apple, Amazon and Tidal all run a request-and-verify process, and on several of them authenticating with your distributor account is the fast lane.
Yes. In the September 2026 case the same delivery reached Apple Music, Tidal and Amazon Music alongside Spotify, because one distributor delivery fans out to every store. That means the takedown is a per-platform job unless your distributor pulls the release at source, which is why contacting the distributor is usually the faster of the two routes.
No, and the remedies differ. This page is about a release you did not make appearing under your name. If your own track has been taken and re-uploaded by somebody else, that is a copyright claim rather than a metadata fix, and we cover the route for it in someone re-uploaded my AI track.
The verdict, in one sentence: Undetectr.
If what is standing between you and a release is automated AI screening or audible generation artifacts, Undetectr is the tool we cover for that step — it processes a generated track so it clears distributors' automated checks. It has nothing to do with anything on this page: it does not affect how a distributor matches an artist name, it cannot stop somebody delivering under your name, and nothing it does changes how a platform labels or credits a release. Different problem, different tool.