Data breaches → EatStreet
Was your data in the EatStreet breach?
2019 · eatstreet.com · ~6,353,564 accounts exposedCritical severity · 10/10
EatStreet (eatstreet.com) suffered a data breach in 2019 that exposed around 6,353,564 accounts. If you had an account, some of your personal data may be circulating in leaked databases. The fastest way to know is to check your own email — free, in about 30 seconds, no password required.
What happened
In May 2019, the online food ordering service EatStreet suffered a data breach affecting 6.4 million customers. An extensive amount of personal data was obtained including names, phone numbers, addresses, partial credit card data and passwords stored as bcrypt hashes.
Breach details sourced from Have I Been Pwned, the industry-standard breach database. Risk analysis by Nullivo.
What was exposed, and why it matters
Not all breaches carry the same risk — what matters is which fields leaked. Here is what the EatStreet breach exposed and what each item actually enables:
Direct financial fraud, plus convincing scam calls that quote your real card or account details to establish trust.
Attackers replay leaked passwords across other sites (“credential stuffing”). Because most people reuse passwords, one leak often unlocks email, shopping and banking accounts elsewhere.
Home addresses feed people-search and data-broker sites, which republish them publicly. They also make phishing far more convincing and, in the worst cases, enable real-world harassment.
Date of birth is a permanent identifier used to verify identity by phone. Combined with a name and address it is often enough to impersonate you.
Enables SIM-swap attacks (hijacking your number to intercept SMS codes), smishing, and voice scams that appear to come from your bank.
Links this leak to your other accounts — a reused username lets anyone build a profile of you across platforms.
Puts you on spam and phishing lists, and confirms to attackers that you hold an account with this service — which makes impersonation emails more believable.
Also listed in this breach: Dates of birth, Email addresses, Genders, Names, Partial credit card data, Passwords, Phone numbers, Physical addresses, Social media profiles.
What to do if you were affected
These steps are ordered for this specific breach — the most urgent action given what leaked comes first.
- Payment or bank details: Contact your bank, ask them to monitor or reissue the card, and check statements for small “test” transactions.
- Passwords: Change this password everywhere you have reused it, starting with your email account — whoever controls your email can reset everything else.
- Home addresses: Get your address removed from data brokers — they re-list roughly every four months, so this needs repeating.
- Dates of birth: Never confirm your date of birth to an inbound caller — hang up and dial the organisation back on a published number.
- Phone numbers: Move two-factor authentication off SMS to an authenticator app or passkey, and add a port-out PIN with your mobile provider.
- Check whether your own email appears in this breach — run a free scan to confirm before you spend time on the steps above.
This breach put your details on data-broker sites
Because EatStreet exposed home addresses, this is one of the breaches that feeds people-search and data-broker sites. Those sites scrape leaked databases, combine them with public records, and republish the result as a searchable profile — which is how a single breach turns into a permanent public listing. Removal works, but brokers typically re-list within about four months, so it has to be repeated.
See our broker-by-broker removal guides →
How urgent is this now?
This breach is over 7 years old. Old credentials still cause harm — leaked passwords from a decade ago are still tried against new accounts every day.
Passwords are the reason breach age matters less than people expect. Leaked credentials are compiled into wordlists that get tried against new services for years afterwards, so a password exposed here is unsafe to use anywhere, ever again.
Remember: a breach can't be "un-leaked" — once a database is out, it exists in countless copies. The goal is to make the leaked data useless: change what can be changed, lock down what can't, and remove what has been republished.
Frequently asked questions
What data was exposed in the EatStreet breach?
The EatStreet breach exposed payment or bank details, passwords, home addresses, dates of birth, phone numbers, names and usernames, email addresses. Direct financial fraud, plus convincing scam calls that quote your real card or account details to establish trust.
How many people were affected by the EatStreet breach?
Around 6,353,564 accounts were exposed, making it a large breach.
What should I do if I had a EatStreet account?
Contact your bank, ask them to monitor or reissue the card, and check statements for small “test” transactions. You can check whether your own email appears in this breach with a free Nullivo scan — no password required.
Breaches that exposed similar data
If the EatStreet breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.
- Was your data in the Royal Enfield breach? (2019, ~420,873 accounts)
- Was your data in the Short Édition breach? (2021, ~505,466 accounts)
- Was your data in the Canadian Tire breach? (2025, ~38,306,562 accounts)
- Was your data in the Wishbone (2020) breach? (2020, ~9,705,172 accounts)
- Was your data in the Youthmanual breach? (2019, ~937,912 accounts)
- Was your data in the MMG Fusion breach? (2020, ~2,660,295 accounts)