Classic site
Lastfm logo

Breach registry

Lastfm Data Breach

Last.fm

last.fm

What was exposed, when it happened, and which databases confirm it.

VerifiedPassword can be found in search
accounts
78,630,418
Breached
March 22, 2012
Last Update
September 20, 2016

Were you caught in this breach?

Search your email, phone number or username against every record CheckLeaked indexes.

Your address never leaves this page: it is hashed in your browser and only a short fragment of that hash is sent.

What happened

In March 2012, the music website Last.fm was hacked and 43 million user accounts were exposed. Whilst Last.fm knew of an incident back in 2012, the scale of the hack was not known until the data was released publicly in September 2016. The breach included 37 million unique email addresses, usernames and passwords stored as unsalted MD5 hashes.

Compromised Info

  • Email addresses
  • Passwords
  • Usernames
  • Website activity

Attestation

Four independent databases catalog this breach and they do not always agree. Each lane below is one source’s own count.

HIBP37,217,682
DEHASHED37,217,682
LEAKCHECK78,630,418
VIGILANTE43,570,957

Sources & Link Methods

  • LeakCheck— linked via automatic string matching
  • Dehashed— linked via domain matching
  • HIBP

FAQ

What was leaked in the Lastfm breach?

The Lastfm breach exposed: Email addresses, Passwords, Usernames, and Website activity.

When did the Lastfm breach happen?

The Lastfm breach was disclosed on March 22, 2012 and affected 78,630,418 records.

Am I affected by the Lastfm breach?

Search your email, phone or username at checkleaked.cc to find out whether your data appears in the Lastfm leak.

Advertising choice

Google Analytics stays active. Allow Google Ads, LinkedIn Ads and Reddit Ads to measure purchases and personalize advertising? Your choice won’t affect search or purchases. You can change it in Settings.

Privacy policy