Was your data in the OGUsers (2019 breach) breach?
Check whether your email address was in it
Check my exposureFree. No password — we email you a six-digit code. This breach and every other one your address appears in.
OGUsers (2019 breach) (ogusers.com) suffered a data breach in 2018 that exposed around 161,143 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 account hijacking and SIM swapping forum OGusers suffered a data breach. The breach exposed a database backup from December 2018 which was published on a rival hacking forum. There were 161k unique email addresses spread across 113k forum users and other tables in the database. The exposed data also included usernames, IP addresses, private messages and passwords stored as salted MD5 hashes.
Breach record from Have I Been Pwned, CC BY 4.0. 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 OGUsers (2019 breach) breach exposed and what each item actually enables:
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. - Private messages
Consider what was discussed on this service and whether anything needs changing (shared passwords, personal disclosures). - 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. - Confirm you were actually in it
Run a free scan before you spend time on the steps above.
How urgent is this now?
This breach is over 8 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 OGUsers (2019 breach) breach?
The OGUsers (2019 breach) breach exposed passwords, private messages, 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 OGUsers (2019 breach) breach?
Around 161,143 accounts were exposed, making it a mid-sized breach.
What should I do if I had a OGUsers (2019 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 OGUsers (2019 breach) breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.