DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

AT&T Mobility reports breach involving service provider employees

Posted on June 19, 2014 by Dissent

So apparently it’s not enough that I read and think about gadzillions of breach notification letters. I’m supposed to actually report on them, too, huh? It seems I was so underwhelmed by an AT&T Mobility breach that I never reported on it here,  even though mainstream media found it really newsworthy, with some even going so far as to suggest that AT&T brought the attack on themselves by its heavy-handed approach to unlocking phones.

To get you all caught up, since I’ve been nudged by a reader to do so: AT&T Mobility disclosed that three employees of an unnamed third-party service provider accessed some customer information during a two-week period in April.  The information included date of birth, Social Security and Customer Proprietary Network Information (which includes the type of information you’d find on your phone bill, like call records). 

The wrongdoers’ goal, AT&T says, was to request codes to unlock phones in the secondary mobile phone market so that those phones could be used with other telecoms.

Those affected were offered free credit monitoring for one year.

AT&T has been coy (translation: non-transparent) about disclosing how many customers were affected, or the name of the third-party provider. Nor have they explained why the third-party provider needed access to customer Social Security numbers.

So why didn’t I tell you about this at the time,  you ask? Well, it’s really nothing new. In 2012,  they disclosed that employees of an unnamed service provider had improperly accessed some customers’ accounts and misused the information. And I recently noted a 22-count indictment against 8 defendants for stealing AT&T customer data  and using the information to make unauthorized wire transfers from the victims’ bank accounts and obtain unauthorized credit or debit cards. One of the defendants was an employee of Interactive Response Technologies, lnc., who provides call center services for AT&T.

So what’s new here? Just that the goal was to unlock phones on the secondary market? Isn’t the real issue that employees of a service provider that they won’t name had access to your Social Security numbers and metadata that could reveal personal information or be misused for other purposes?  AT&T has a lot of service providers, I would imagine.  Who runs the criminal background checks on their employees? The service providers? AT&T?  What can – and will – AT&T do to prevent more of these types of breaches?  How protected are your SSN and why can’t we get Congress to outlaw the use of SSNs for commercial purposes?

 

 


Related:

  • Resource: NY DFS Issues New Cybersecurity Guidance to Address Risks Associated with the Use of Third-Party Service Providers
  • KT Chief to Resign After Cybersecurity Breach Resolution
  • Cyber-Attack On Bectu’s Parent Union Sparks UK National Security Concerns
  • A business's cyber insurance policy included ransom coverage, but when they needed it, the insurer refused to pay. Why?
  • Before Their Telegram Channel Was Banned Again, ScatteredLAPSUS$Hunters Dropped Files Doxing Government Employees (2)
  • Capita hit with £14m fine for personal data breach in 2023 cyber attack
Category: Breach IncidentsInsiderSubcontractor

Post navigation

← US Marshal CCs, rather than BCCs, those interested in anonymous Bitcoin auction
LinkedIn vulnerability to MITM attacks puts your data at risk – Zimperium →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs
  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says
  • The Case for Making EdTech Companies Liable Under FERPA
  • NHS providers reviewing stolen Synnovis data published by cyber criminals

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation
  • Who’s watching the watchers? This Mozilla fellow, and her Surveillance Watch map

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[at]databreaches.net
Mastodon: Infosec.Exchange/@PogoWasRight
Signal: +1 516-776-7756
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.