Data breaches → JobStreet
Was your data in the JobStreet breach?
2012 · jobstreet.com · ~3,883,455 accounts exposedCritical severity · 10/10
JobStreet (jobstreet.com) suffered a data breach in 2012 that exposed around 3,883,455 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 October 2017, the Malaysian website lowyat.net ran a story on a massive set of breached data affecting millions of Malaysians after someone posted it for sale on their forums. The data spanned multiple separate breaches including the JobStreet jobs website which contained almost 4 million unique email addresses. The dates in the breach indicate the incident occurred in March 2012. The data later appeared freely downloadable on a Tor hidden service and contained extensive information on job seekers including names, genders, birth dates, phone numbers, physical addresses and passwords.
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 JobStreet breach exposed and what each item actually enables:
The strongest identity-theft material there is — enough to open credit accounts or file fraudulent claims in your name.
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.
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.
Also listed in this breach: Dates of birth, Email addresses, Genders, Geographic locations, Government issued IDs, Marital statuses, Names, Nationalities, Passwords, Phone numbers, Physical addresses, 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.
- Government identifiers: Consider a credit freeze or fraud alert with the credit reference agencies, and watch for accounts you did not open.
- 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 JobStreet 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 14 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 JobStreet breach?
The JobStreet breach exposed government identifiers, passwords, home addresses, dates of birth, phone numbers, location data, names and usernames, email addresses. The strongest identity-theft material there is — enough to open credit accounts or file fraudulent claims in your name.
How many people were affected by the JobStreet breach?
Around 3,883,455 accounts were exposed, making it a large breach.
What should I do if I had a JobStreet account?
Consider a credit freeze or fraud alert with the credit reference agencies, and watch for accounts you did not open. 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 JobStreet breach affected you, these breaches exposed comparable information — worth checking too, since leaked datasets are routinely combined.
- Was your data in the VNG breach? (2015, ~24,853,850 accounts)
- Was your data in the Qatar National Bank breach? (2015, ~88,678 accounts)
- Was your data in the Ajarn breach? (2018, ~266,399 accounts)
- Was your data in the Upstox breach? (2021, ~111,002 accounts)
- Was your data in the Ashley Madison breach? (2015, ~30,811,934 accounts)
- Was your data in the Sony breach? (2011, ~37,103 accounts)