DataBreaches.Net

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

AT&T Notifying some wireless customers of vendor incident

Posted on March 9, 2023 by Dissent

AT&T has been notifying some wireless customers of an incident involving an unnamed vendor.

Email from AT&T informs them of vendor incident. In a notice sent to a customer who shared it with DataBreaches, AT&T wrote:

AT&T’s commitment to customer privacy and data security is a top priority. We recently determined that an unauthorized person breached a vendor’s system and gained access to your “Customer Proprietary Network Information” (CPNI). In our industry, CPNI is information related to the telecommunications services you purchase from us, such as the number of lines on your account or the wireless plan to which you are subscribed. However, please rest assured that no sensitive personal or financial information such as Social Security number or credit card information was accessed.

To address this issue, the following steps have been taken:

  • We confirmed with the vendor that the vulnerability has been fixed.
  • We have notified federal law enforcement about the unauthorized access of your CPNI as required by the Federal Communications Commission. Our report to law enforcement does not contain specific information about your account, only that the unauthorized access occurred.

If you have an existing account with AT&T, you may want to consider adding our “extra security” password protection to the account at no cost. You can learn more at https://www.att.com/support/article/my-account/KM1051397/

Please accept our apology for this incident. If you have further questions, you may visit: https://att.com/data-event/login You will be prompted for your myAT&T login credentials, and if you do not have a myAT&T profile, you can create one using your account information.

Thank you,

AT&T

AT&T did not reveal the vendor’s identity other than to say it was a marketing vendor and the incident occurred in January.

On their site with additional information on the incident, AT&T states that the exposed information included customer’s first name, wireless account number, wireless phone number and email address.

“It also included the number of lines on the account and basic device (e.g., iPhone 7) and installment agreement information that was used to help indicate device upgrade eligibility. A small percentage of impacted customers also had exposure or rate plan name, past due amount, monthly payment amount, various monthly charges and/or minutes used.”

Of note, they indicate that the customer information was several years old, and “No credit card information, SSN, date of birth, account passwords or specific device IDs (e.g., IMEI or SIM) were involved.”

DataBreaches sent an inquiry to AT&T asking how many customers were notified of this incident. No reply was immediately provided.

Update of March 10: BleepingComputer reports that approximately 9 million wireless accounts were accessed. AT&T did not reply to the inquiry sent on March 9.

No related posts.

Category: Breach IncidentsBusiness SectorHackU.S.Unauthorized Access

Post navigation

← Co-Working for the Ransomware Age: How Hive Thrived
Asante Notifies More than 8,800 Patients Whose Records Appeared to Be Inappropriately Accessed by a Physician →

2 thoughts on “AT&T Notifying some wireless customers of vendor incident”

  1. Roger says:
    March 11, 2023 at 2:35 pm

    where the link text says https://www.att.com/support/article/my-account/KM1051397/ its a link to your mailbox and thus not clickable.

    1. Dissent says:
      March 11, 2023 at 4:07 pm

      Oops… yes, I had removed the sender’s real acct info but then forgot to unlink the resulting non-working link. Have done that now, thanks.

Comments are closed.

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

  • Mississippi Law Firm Sues Cyber Insurer Over Coverage for Scam
  • Ukrainian Hackers Wipe 47TB of Data from Top Russian Military Drone Supplier
  • Computer Whiz Gets Suspended Sentence over 2019 Revenue Agency Data Breach
  • Ministry of Defence data breach timeline
  • Hackers Can Remotely Trigger the Brakes on American Trains and the Problem Has Been Ignored for Years
  • Ransomware in Italy, strike at the Diskstation gang: hacker group leader arrested in Milan
  • A year after cyber attack, Columbus could invest $23M in cybersecurity upgrades
  • Gravity Forms Breach Hits 1M WordPress Sites
  • Stormous claims to have protected health info on 600,000 patients of North Country Healthcare. The patient data appears fake. (2)
  • Back from the Brink: District Court Clears Air Regarding Individualized Damages Assessment in Data Breach Cases

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

  • The EU’s Plan To Ban Private Messaging Could Have a Global Impact (Plus: What To Do About It)
  • A Balancing Act: Privacy Issues And Responding to A Federal Subpoena Investigating Transgender Care
  • Here’s What a Reproductive Police State Looks Like
  • Meta investors, Zuckerberg to square off at $8 billion trial over alleged privacy violations
  • Australian law is now clearer about clinicians’ discretion to tell our patients’ relatives about their genetic risk
  • The ICO’s AI and biometrics strategy
  • Trump Border Czar Boasts ICE Can ‘Briefly Detain’ People Based On ‘Physical Appearance’

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[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.