Classic site
Gett logo

Breach registry

Gett Data Breach

Ge.tt

ge.tt

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

VerifiedPassword can be found in search
accounts
3,424,634
Breached
May 4, 2017
Last Update
February 22, 2021

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 May 2017, the file sharing platform Ge.tt suffered a data breach. The data was subsequently put up for sale on a dark web marketplace in February 2019 alongside a raft of other breaches. The Ge.tt breach included names, social media profile identifiers, SHA256 password hashes and almost 2.5M unique email addresses. The data was provided to HIBP by a source who requested it be attributed to BreachDirectory.

Compromised Info

  • Email addresses
  • Names
  • Passwords
  • Social media profiles

Attestation

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

HIBP2,481,121
DEHASHED2,481,121
LEAKCHECK3,424,634
VIGILANTE1,825,477

Sources & Link Methods

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

FAQ

What was leaked in the Gett breach?

The Gett breach exposed: Email addresses, Names, Passwords, and Social media profiles.

When did the Gett breach happen?

The Gett breach was disclosed on May 4, 2017 and affected 3,424,634 records.

Am I affected by the Gett breach?

Search your email, phone or username at checkleaked.cc to find out whether your data appears in the Gett 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