Data breaches → Bell (2017 breach)
Was your data in the Bell (2017 breach) breach?
2017 · bell.ca · ~2,231,256 accounts exposedCritical severity · 10/10
Bell (2017 breach) (bell.ca) suffered a data breach in 2017 that exposed around 2,231,256 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 2017, the Bell telecommunications company in Canada suffered a data breach resulting in the exposure of millions of customer records. The data was consequently leaked online with a message from the attacker stating that they were "releasing a significant portion of Bell.ca's data due to the fact that they have failed to cooperate with us" and included a threat to leak more. The impacted data included over 2 million unique email addresses and 153k survey results dating back to 2011 and 2012. There were also 162 Bell employee records with more comprehensive personal data including names, phone numbers and plain text "passcodes". Bell suffered another breach in 2014 which exposed 40k records.
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 Bell (2017 breach) breach exposed and what each item actually enables:
Attackers replay leaked passwords across other sites (“credential stuffing”). Because most people reuse passwords, one leak often unlocks email, shopping and banking accounts elsewhere.
Enables SIM-swap attacks (hijacking your number to intercept SMS codes), smishing, and voice scams that appear to come from your bank.
Reveals where you live, work or travel, which supports both targeted scams and physical-safety risks.
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.
Reveals your approximate location and internet provider, which adds credibility to targeted scams.
Also listed in this breach: Email addresses, Geographic locations, IP addresses, Job titles, Names, Passwords, Phone numbers, Spoken languages, Survey results, Usernames.
What to do if you were affected
These steps are ordered for this specific breach — the most urgent action given what leaked comes first.
- Passwords: Change this password everywhere you have reused it, starting with your email account — whoever controls your email can reset everything else.
- Phone numbers: Move two-factor authentication off SMS to an authenticator app or passkey, and add a port-out PIN with your mobile provider.
- Location data: Review location sharing on the accounts you still hold with this service.
- Names and usernames: Search your usual username to see what else it exposes, and use distinct handles for sensitive accounts.
- Email addresses: Treat any message referencing this service with suspicion, and never act on links in unexpected emails.
- Check whether your own email appears in this breach — run a free scan to confirm before you spend time on the steps above.
How urgent is this now?
This breach is over 9 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 Bell (2017 breach) breach?
The Bell (2017 breach) breach exposed passwords, phone numbers, location data, names and usernames, email addresses, ip addresses. Attackers replay leaked passwords across other sites (“credential stuffing”). Because most people reuse passwords, one leak often unlocks email, shopping and banking accounts elsewhere.
How many people were affected by the Bell (2017 breach) breach?
Around 2,231,256 accounts were exposed, making it a large breach.
What should I do if I had a Bell (2017 breach) account?
Change this password everywhere you have reused it, starting with your email account — whoever controls your email can reset everything else. 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 Bell (2017 breach) breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.
- Was your data in the IIMJobs breach? (2018, ~4,216,063 accounts)
- Was your data in the Gaadi breach? (2015, ~4,261,179 accounts)
- Was your data in the Wishbone (2020) breach? (2020, ~9,705,172 accounts)
- Was your data in the CyberServe breach? (2021, ~1,107,034 accounts)
- Was your data in the Dubsmash breach? (2018, ~161,749,950 accounts)
- Was your data in the Liker breach? (2021, ~465,141 accounts)