LiveBreach Intelligence: data breaches, leaks & ransomware, tracked as they surfaceOngoing protection: GalaxyWarden →
Recent BreachesData breach tracker

Recent Breaches › JobStreet Data Breach (2012)

CRITICAL severityConfirmedHow we verify

JobStreet Data Breach (2012): What Was Exposed & What To Do

RBRecent Breaches Breach Intelligence·March 7, 2012

SourceBreach data provided in part by Have I Been Pwned, used under CC BY 4.0.

JobStreet Data Breach (2012)

Reported March 7, 2012. Approximately 3.9M people affected.

CRITICAL
Severity
3.9M
People affected
12
Data types exposed
March 7, 2012
Disclosed
ShareXLinkedInFacebookRedditWhatsAppTelegram

The JobStreet Data Breach (2012) (reported March 7, 2012) exposed Dates of birth, Email addresses, Genders and Geographic locations belonging to roughly 3.9M people. If you have an account with them, your information may now be circulating on the open web and with data brokers. Here’s exactly what happened, how to check if you were affected, and what to do next.

Severity & verification
CRITICAL severityConfirmed
Account credentials exposed.
Corroborated by an official disclosure or a verified breach feed.
Was your email in the JobStreet Data Breach (2012) breach?
3.9M accounts were exposed here. See if yours is one — and every other breach it’s in. 15-sec check, no card.

By running your scan you agree to the Terms and Conditions and the Privacy Policy, and to GalaxyWarden emailing you the results of this scan.

Millions of people who used a major Southeast Asian jobs platform more than a decade ago may still face risks from the exposure of personal records that included government-issued identification and contact details. The incident, which affected approximately 3.9 million individuals, came to wider public attention years after the data first appeared in underground channels.

Because the records contained names, dates of birth, email addresses and official identifiers, they remain potentially useful for identity-related misuse long after the original compromise.

Breaking down the breach

The JobStreet data breach is dated to March 2012. Public reporting of the incident occurred in October 2017 when a Malaysian technology news site described a large collection of records that had been offered for sale on an online forum. The collection included material from several separate incidents, one of which originated from the JobStreet service and contained nearly four million unique email addresses.

The data later became available for free download on a Tor hidden service. No official statement from the organisation at the time of the 2017 reporting confirmed the method or precise date of the intrusion, and the total number of records ultimately confirmed as exposed remains limited to the 3.9 million figure associated with the JobStreet portion.

How a breach like this happens

Incidents involving job-seeking platforms commonly begin with attackers gaining unauthorised access to databases that store user profiles. Once inside, the actors can copy large volumes of structured records without immediate detection if logging or monitoring controls are insufficient.

The stolen files are then packaged and circulated through forums or hidden services, sometimes offered for sale before appearing in public archives. Because employment sites routinely retain historical user data for extended periods, older breaches can resurface years later when the material is rediscovered or re-shared.

About JobStreet

JobStreet operated as an online recruitment service connecting employers with job seekers across several countries in the Asia-Pacific region. Like similar platforms, it collected detailed personal information from individuals creating accounts or submitting applications, including contact details, demographic fields and official identifiers required for employment processes.

A breach at such a service is consequential because the records often combine multiple categories of identifying information that are not frequently changed, such as dates of birth and government-issued numbers, and because users may have submitted the same details to multiple employment sites over time.

What was likely exposed

The records associated with the JobStreet portion of the 2017 disclosure included dates of birth, email addresses, genders, geographic locations, government-issued IDs, marital statuses, names and nationalities. Contemporary descriptions of the files also referenced phone numbers, physical addresses and passwords, although the precise fields present in every record have not been independently verified by the organisation.

Exact confirmation of which additional data elements were present for all 3.9 million affected individuals remains limited to the information published in 2017.

Why it matters

Records that combine names, official identifiers and contact information can be used to support targeted phishing, account takeover attempts or the construction of synthetic identities. Because the material has circulated on hidden services, copies may persist beyond any single takedown effort.

For the organisation, the incident illustrates the long-term liability that accompanies the storage of employment-related personal data, even when the original compromise occurred more than five years before public reporting.

What to do if you're exposed

Individuals who believe their information may have been included should change passwords on any accounts that reuse credentials from the affected period and enable multi-factor authentication where available. Monitoring credit files or official identity registries for unusual activity provides an additional layer of oversight.

Readers can run a free exposure scan of their email address against known breach data sets to determine whether their details appear in publicly documented incidents.

AICompiled with AI assistance from public sources and published under our editorial standards.

Editorial & sourcing policy
Recent Breaches is a breach-monitoring service and news aggregator. We do not exfiltrate, host, purchase, or redistribute stolen data, and we do not hold the data claimed in leak-site listings. Incidents are compiled from publicly accessible sources and threat-intelligence platforms and are reported as claims attributed to their source. We promptly correct or remove material shown to be inaccurate — write to support@galaxywarden.com or press@recentbreaches.com.
Check if you’re exposed →

How this breach connects

Company

Method

CompanyJobStreet security record
73/100
DoxxScan™ · Moderate doxx risk
C- 64Below-average record

1 reported incident on record.

See JobStreet’s full breach history →

More recent breaches

Heroes of Newerth Data Breach (2012)December 17, 2012BookCrossing Data Breach (2012)November 5, 2012Netlog Data Breach (2012)November 1, 2012Lookbook Data Breach (2012)August 24, 2012

Latest breaches

Read GalaxyWarden’s full analysis of the JobStreet Data Breach (2012) →

Verified breach. Breach data provided in part by Have I Been Pwned, used under CC BY 4.0.

Breach listings — particularly those originating from ransomware or leak sites — are third-party claims that may be unverified, incomplete, or inaccurate. A listing does not by itself confirm that a breach occurred or that any specific data was exposed. Severity is an automated assessment, not a definitive rating. Verification status is shown where available.

Attributions to threat groups and methods reflect public reporting and, in some cases, unverified claims made by the groups themselves; they may be incomplete or later revised. Recent Breaches and GalaxyWarden are independent and are not affiliated with, and do not endorse, any company or group named on this page. This information is aggregated from public sources for awareness only and is not legal, security, or investment advice.

ShareXLinkedInFacebookRedditWhatsAppTelegram