DataBreaches.Net

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

Experian reports another breach of its credit report database (update 2)

Posted on September 20, 2013 by Dissent

I haven’t been seeing as many breach reports by Experian this year, which could be a good sign, although it just could be that some states haven’t updated their breach lists in while.

In any event, one just showed up on New Hampshire’s site that elevated an eyebrow.

In a letter dated September 16 signed by L. Mundy, Vice President, Regulatory Compliance, Experian writes that between August 26 and August 27, consumers “may” have had their personal information accessed, including name, address, Social Security number, and/or account numbers. I’ve never understood why Experian’s letters of this kind underscore “may” when their cover letter to the state says that they are notifying residents of “unauthorized access” (as opposed to “possible unauthorized access”).  Whenever I see Experian write to consumers that their info “may” have been accessed, I’d like to ask “Why don’t you know for sure? Don’t your access logs show whether a consumer’s report was accessed or not?”

In any event, Experian’s letter states they had identified that “its client, Defense Contracts South FCU, had certain Experian consumer information accessed without proper authorization.” Experian is working with Texas-based Defense Contracts South FCU and law enforcement to investigate.

Experian’s letter, taken in the context of approximately 100 letters of this kind that I have seen them send in the past,  suggests that someone may have compromised Defense Contracts South’s login credentials to the database.

What surprised me a bit was Experian’s  offer of two years’ complimentary enrollment in ProtectMyID Alert. That was not their typical offer in the past. Whether that means that they think this breach may be more serious or whether they have just changed their incident response plan is unknown to me.

Update: This breach was also reported as affecting 6 Maryland residents.

 Update 2:  Okay, so Experian did have at least two other incidents as two breach reports from July and September have been added to Maryland’s breach tool. In these cases, though, others were able to successfully authenticate as the consumers sometime between June 21 and June 24 in the first case and July 2 to July 29 in the second case.. Once again, the letter tells the consumer their information “may” have been accessed without authorization. Why doesn’t the letter ask the consumer whether they gave anyone their information to access their information?  Perhaps some these letters should read, “If you did not authorize someone to access your information between June 21 and June 24, then we regret to inform you that….”  In both cases, affected consumers were offered two years of free credit monitoring, so that they may just be their routine response.


Related:

  • ModMed revealed they were victims of a cyberattack in July. Then some data showed up for sale.
  • Toys “R” Us Canada customers notified of breach of personal information
  • Gatineau gymnastics centre warns members of possible data breach
  • Confidence in ransomware recovery is high but actual success rates remain low
  • Protected health information of 462,000 members of Blue Cross Blue Shield of Montana involved in Conduent data breach
  • Resource: NY DFS Issues New Cybersecurity Guidance to Address Risks Associated with the Use of Third-Party Service Providers
Category: Breach IncidentsBusiness SectorCommentaries and AnalysesFinancial Sector

Post navigation

← MN: Judge tosses data breach suit against state
Missing Allscripts backup drive held Mercy Health Systems patient information →

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

  • 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
  • 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

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

  • Lawmakers Warn Governors About Sharing Drivers’ Data with Federal Government
  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • 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

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.