DataBreaches.Net

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

T-Mobile case update: indicted men were not employees

Posted on March 3, 2009 by Dissent

As an update to the story here:

A spokesperson for the U.S. Attorney’s Office informs me that the 5 men who were indicted today were not employees of T-Mobile. They allegedly accessed and acquired the customer data via an authorization code that they obtained from the owner of a T-Mobile store. The owner of that store has not been identified or charged in the case.

The indictment is available here. Keeping in mind that an indictment is not a conviction and that everyone’s presumed innocent until proven guilty, the indictment suggests that sometime beginning in October 2005 and continuing into February 2006, the five indictees may have been accessing T-Mobile customer data including their SSN and credit ratings. They allegedly then used PrivateEye.com to obtain addition personal information about the customers they intended to victimize such as addresses and dates of birth and other personal information.

I’ve requested some additional information from T-Mobile and may have further updates to this story.


Related:

  • Veradigm's Breach Claims Under Scrutiny After Dark Web Leak
  • Massive Great Firewall Leak Exposes 500GB of Censorship Data
  • Snowflake Loses Two More Bids to Dismiss Data Breach Plaintiffs
  • US company with access to biggest telecom firms uncovers breach by nation-state hackers
  • UK: FCA fines former employee of Virgin Media O2 for data protection breach
  • The 4TB time bomb: when EY's cloud went public (and what it taught us)
Category: Breach IncidentsBusiness SectorID TheftU.S.Unauthorized Access

Post navigation

← T-mobile customer data used in fraud; 5 indicted
Western Oklahoma State College alerts library users of data breach →

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

  • Checkout.com Discloses Data Breach After Extortion Attempt
  • Washington Post hack exposes personal data of John Bolton, almost 10,000 others
  • Draft UK Cyber Security and Resilience Bill Enters UK Parliament
  • Suspected Russian hacker reportedly detained in Thailand, faces possible US extradition
  • Did you hear the one about the ransom victim who made a ransom installment payment after they were told that it wouldn’t be accepted?
  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • 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

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

  • Once a Patient’s in Custody, ICE Can Be at Hospital Bedsides — But Detainees Have Rights
  • OpenAI fights order to turn over millions of ChatGPT conversations
  • Maryland Privacy Crackdown Raises Bar for Disclosure Compliance
  • Lawmakers Warn Governors About Sharing Drivers’ Data with Federal Government
  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools

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.