Data breaches → PPCGeeks
Was your data in the PPCGeeks breach?
2016 · ppcgeeks.com · ~492,518 accounts exposedCritical severity · 10/10
PPCGeeks (ppcgeeks.com) suffered a data breach in 2016 that exposed around 492,518 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 August 2016, the pocket PC fan site forum PPCGeeks suffered a data breach that exposed over 490k records. The breach of the vBulletin forum exposed email and IP addresses, usernames, dates of birth and passwords stored as salted MD5 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 PPCGeeks 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.
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.
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.
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.
- Dates of birth: Never confirm your date of birth to an inbound caller — hang up and dial the organisation back on a published number.
- 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.
- IP addresses: No direct action needed, but be wary of anyone quoting your location as “proof” of identity.
- 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 10 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 PPCGeeks breach?
The PPCGeeks breach exposed passwords, dates of birth, 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 PPCGeeks breach?
Around 492,518 accounts were exposed, making it a mid-sized breach.
What should I do if I had a PPCGeeks 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 PPCGeeks breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.
- Was your data in the Nulled.cr breach? (2016, ~599,080 accounts)
- Was your data in the Anime-Planet breach? (2016, ~368,507 accounts)
- Was your data in the MrExcel breach? (2016, ~366,140 accounts)
- Was your data in the dBforums breach? (2016, ~363,468 accounts)
- Was your data in the GPS Underground breach? (2016, ~669,584 accounts)
- Was your data in the Facepunch breach? (2016, ~342,913 accounts)