Hackers Just Scraped 86 Million Songs From Spotify

Anna’s Archive used distributed accounts and API abuse to extract 300 terabytes of protected audio content

Alex Barrientos Avatar
Alex Barrientos Avatar

By

Our editorial process is built on human expertise, ensuring that every article is reliable and trustworthy. AI helps us shape our content to be as accurate and engaging as possible.
Learn more about our commitment to integrity in our Code of Ethics.

Image: Wikimedia

Key Takeaways

Key Takeaways

  • Anna’s Archive scraped 86 million Spotify songs using distributed user accounts
  • Hackers bypassed DRM through legitimate-looking API abuse rather than server infiltration
  • Streaming platforms may implement stricter verification following this 300-terabyte security breach

Your Spotify Wrapped just became someone else’s complete music library. Anna’s Archive—the shadow librarians behind massive book piracy operations—claims it scraped 86 million songs from Spotify, capturing 99.6% of actively-listened tracks in a 300-terabyte digital heist that makes typical music piracy look quaint.

The numbers sound impossible until you realize they’re not. This hacktivist collective didn’t breach Spotify’s servers. Instead, they gamed the system from the inside, using distributed user accounts to systematically extract protected audio files over months of coordinated scraping.

How Consumer-Grade Tools Became Industrial Weapons

Account farming and API abuse turned streaming protection into paper shields.

The extraction combined “public APIs, token abuse, rate-limit evasion, and DRM bypass techniques” according to security analysts—essentially weaponizing the same mechanisms you use to sync playlists across devices. Anna’s Archive discovered how to scale this approach industrially, circumventing digital rights management through legitimate-looking user behavior rather than Hollywood-style server infiltration.

Spotify confirmed it “identified and disabled the nefarious user accounts” involved, suggesting the breach operated through distributed credential abuse rather than a single point of failure. Popular tracks were preserved at Spotify’s native 160 kbps quality, while obscure songs got compressed to 75 kbps—a curatorial decision that reveals just how methodically this operation was planned.

Digital Preservation Meets Copyright Reality

Noble intentions don’t neutralize legal consequences for massive rights violations.

Anna’s Archive frames this as cultural preservation, claiming “huge chunks of lesser-known music could disappear if music streaming platforms pull the plug or lose licenses.” It’s the same rationale they’ve used for archiving academic papers and books—protecting humanity’s cultural output from corporate gatekeeping.

But copyright law doesn’t care about good intentions. This 300-terabyte archive represents industrial-scale infringement that threatens the licensing agreements keeping artists paid and platforms operational. Spotify’s response—implementing “new safeguards for anti-copyright attacks”—suggests the company is taking heat from record labels who trusted their content to remain protected.

What This Means for Your Music Future

Platform security vulnerabilities could reshape how streaming services operate.

This incident exposes fundamental weaknesses in how streaming platforms protect licensed content. When consumer-facing features can be systematically exploited for mass extraction, every major platform becomes vulnerable to similar attacks.

Expect streaming services to implement stricter account verification and API limitations—changes that might make your music experience less seamless. The real question isn’t whether Anna’s Archive will face legal consequences, but whether this blueprint inspires copycat operations targeting other platforms.

Share this

At Gadget Review, our guides, reviews, and news are driven by thorough human expertise and use our Trust Rating system and the True Score. AI assists in refining our editorial process, ensuring that every article is engaging, clear and succinct. See how we write our content here →