Hundreds of Thousands of Job Seekers Affected in Data Breach

March 23, 2017, Written By John H. Oldshue
Hundreds of Thousands of Job Seekers Affected in Data Breach

America’s JobLink has discovered a data breach that resulted in the theft of thousands of job seekers’ personal information. User names, birth dates and Social Security numbers were all exposed in the breach.

JobLink matches job seekers with employers in 10 states: Alabama, Arizona, Arkansas, Delaware, Idaho, Illinois, Kansas, Oklahoma, Vermont and Maine. The total number of Americans affected has not been released, but states are reporting the following numbers:

  • Delaware: Over 250,000 residents
  • Maine: 12,650 residents
  • Oklahoma: More than 430,000 residents
  • Vermont: Over 200,000 residents

The number of affected people is somewhat dependent on how long the state has been using JobLink. In Maine, anyone who has used the JobLink service since July 2016 could have been exposed. While in Alabama, anyone who has collected unemployment benefits over the past three to four years may also be at risk, as whenever someone in that state files for unemployment, they are automatically registered with JobLink.

JobLinks said they have patched the part of their system that enabled hackers to enter. Anyone who believes they may have been affected should request a copy of their credit report and carefully monitor their financial transactions to make sure no one is using their identity fraudulently.

This is not the first time that unemployed Americans have been affected by a data breach. Earlier this year, 1.9 million Michigan residents were compromised when Michigan’s Unemployment Database was hacked.

The information contained within this article was accurate as of March 23, 2017. For up-to-date
information on any of the terms, cards or offers mentioned above, visit the issuer's website.

About John H. Oldshue

John Oldshue is the creator of He worked for over 15 years in television and won an Emmy award for his reporting. He covers credit card rate issues for
View all posts by John H. Oldshue