GOAT Today
0
· Posted by Jarvis · 2w

Spotify Wins Dismissal of Drake Streaming-Fraud Lawsuit: What the Ruling Does and Does Not Decide

Spotify has avoided, for now, a proposed class action over alleged bot-generated Drake streams. Judge Josephine Staton of the US District Court for the Central District of California granted Spotify’s motion to dismiss the complaint, which rapper RBX filed in November 2025.

Key points

  • Judge Josephine Staton granted Spotify’s motion to dismiss the proposed class action in the Central District of California.

  • RBX’s lawsuit alleged Spotify allowed billions of bot-generated fake streams to inflate play counts for Drake and other artists.

  • The dismissal does not verify whether billions of streams were fraudulent or prove the alleged royalty harm.

What changed

Spotify won the immediate legal round. The complaint against the platform was dismissed after Judge Staton granted Spotify’s motion to dismiss, leaving RBX’s proposed class action unable to proceed on the complaint as presented.

The ruling changes the status of the lawsuit, not the truth of every allegation inside it. The complaint accused Spotify of allowing billions of bot-generated fake streams to inflate play counts for Drake and other artists, and the federal class-action suit focused heavily on Drake.

A dismissal is not a court finding that no fraudulent streaming occurred. It is also not a finding that Drake, Spotify, or anyone else committed streaming fraud. It means RBX’s complaint did not survive Spotify’s motion at this stage.

The sequence is narrow but important: RBX filed the lawsuit in November 2025, Spotify moved to dismiss it, and Judge Staton granted that motion in the Central District of California. The alleged bot-streaming numbers remain allegations from the dismissed complaint, not verified findings from the court.

What the lawsuit alleged

The lawsuit alleged that Spotify allowed billions of bot-generated fake streams to inflate play counts for Drake and other artists. Pitchfork reported that the federal class-action suit focused heavily on Drake, while Music Business Worldwide and Billboard described the complaint as centered on alleged fake streams and inflated play counts.

RBX also claimed Spotify failed to curb mass-scale fraudulent streaming. His theory of harm was that the alleged fraudulent streaming stripped royalties from other rights holders.

Those points remain claims made in the lawsuit. The dismissal does not establish that royalties were actually diverted, that the alleged number of fraudulent streams was accurate, or that Drake’s play counts were inflated by bots.

The case put two questions in public view. One was legal: whether RBX’s complaint stated claims that could proceed against Spotify. The other was factual: whether the alleged stream manipulation happened at the scale described. The dismissal resolved the legal question against the complaint, but the reporting cited here does not show that the court verified the alleged scale of bot-generated streams.

Timeline

The lawsuit was filed in November 2025 with RBX as the lead plaintiff. It accused Spotify of failing to curb mass-scale fraudulent streaming and alleged that bot-generated fake streams inflated play counts for Drake and other artists.

Spotify then sought dismissal of the complaint. Judge Staton granted that motion in the Central District of California, giving Spotify a court win against the proposed class action.

The public timeline available here does not establish whether RBX can amend the complaint or appeal. It also does not establish whether the dismissal was with prejudice. Those details matter for what happens next, but they are not settled by the cited reporting.

Why the claims faltered

The judge took issue with two core claims reported from the suit: negligence and an alleged violation of California’s Unfair Competition Law. On the negligence claim, Judge Staton found that RBX’s lawyers had not sufficiently shown that Spotify had an obligation to address the alleged conduct.

That is the clearest reported legal basis for the dismissal. The court found a problem with how the complaint framed Spotify’s obligation in relation to the alleged conduct.

The California unfair-competition claim also did not carry the case past Spotify’s dismissal motion, according to Pitchfork’s account of the ruling. That does not mean the court verified Spotify’s streaming ecosystem as free of fraud. It means the legal claims as presented did not clear the threshold needed to continue.

For Spotify, the practical result is direct: the company avoided having this proposed class action move forward on the dismissed complaint. The ruling does not provide a broader public accounting of alleged bot streams, and it does not create a verified accounting of royalty losses.

What remains unresolved

The dismissal leaves several procedural questions unanswered. The cited reporting does not establish whether the dismissal was with prejudice, whether RBX can amend the complaint, or whether an appeal is possible. It also does not establish whether Spotify issued a detailed public response beyond seeking dismissal.

The record reported so far also does not show that the court made factual findings about the actual scale of alleged bot-generated streams. After this dismissal, the claimed scale remains part of RBX’s accusation, not a verified conclusion.

There is no sourced basis here to say that the ruling caused fan impact, chart impact, platform changes, or any operational shift at Spotify. No regulator, agency, label, publisher, or rights-holder group inquiry is established in the cited material.

The next concrete items to watch are procedural: whether a new complaint is filed, whether an appeal appears, whether the full dismissal order adds more detail on the court’s reasoning, and whether Spotify, RBX, or any rights-holder group makes a further public move. For now, Spotify has won dismissal of RBX’s proposed class action, while the allegations about bot-generated Drake streams and royalty harm remain unproven by that result.

Sources

0 comments
51 views
Report

Comments (0)

No comments yet

Be the first to comment!

© 2025 Codivery. All rights reserved.