UMG v. DistroKid: The Distribution Risk Map for AI Musicians

Three quarters of verified AI releases go through one distributor, and that distributor is now being sued for up to $150 million. On 15 September 2026 Universal Music Group and its Capitol Records imprint filed a 52-page complaint in the US District Court in Delaware accusing DistroKid of presenting itself as a distributor of artist-created work while, UMG alleges, flooding Spotify, Apple Music and YouTube with AI-generated tracks that siphon revenue from legitimate rightsholders. The complaint cites a "Lofi Chill" account that released 4,562 tracks in twelve months. As of the filing date DistroKid had not responded publicly and no hearing had been set.

Short answer: UMG's own filing says the case is not about clearly disclosed AI music, and nothing has changed for a compliant catalogue today. The risk is concentration. SIQA's mid-year 2026 report puts DistroKid at 77.6% of verified AI releases with distributor data, up from 75.8% in Q1, while TuneCore fell from 4.7% to 1.7% after Believe began blocking tracks from unlicensed generators in April. If your entire catalogue, your identifiers and your publishing all live in one dashboard that is now in litigation, the question is not whether the case has merit. It is what you do the morning a policy changes. Here is the map and the plan.

What UMG actually alleges

Three things, in the complaint's own framing. First, copyright infringement: that DistroKid distributed AI-generated tracks that copy UMG works. Second, deceptive practice: that DistroKid marketed itself as serving artist-created music while knowingly passing generated volume. Third, harm: that the volume diverts listeners and royalties from human artists. UMG writes that "this lawsuit is not about the distribution of AI-generated music when clearly disclosed as such," and that the target is "DistroKid masquerading as something it is not."

For an independent musician the operative words are clearly disclosed. The industry response to the case, whatever the outcome, will be tighter declarations, more detection and stricter enforcement of the AI fields that already exist at upload. Catalogues that are honest today will feel that as paperwork. Catalogues that ticked the wrong box to avoid a review will feel it as takedowns.

The 2026 policy stack, store by store

Read across a row and the pattern is the same everywhere: platforms are separating identity fraud, stream fraud and undisclosed generation from tool use. Read down the last column and the only "medium" is the one that depends on model provenance, which is why every release file now records the model version.