DataBreaches.Net

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

Additional information on the Wyndham breach

Posted on January 13, 2009 by Dissent

As a follow-up to the blog entry on a hack of Wyndham, a copy of their October notification sent to at least one state attorney general is now available online. That notification indicates that:

In mid-September, a WHR [Wyndham Hotels and Resorts] data center administrator detected unusual activity on one of the company servers located in Phoenix, AZ and notified the internal information security team. WHR then retained an external security forensics expert to conduct a thorough investigation, which is still continuing. Our investigation to date has confirmed that a sophisticated hacker penetrated the computer systems of one of the WHR franchised hotels and thereafter was able to create a unique file containing credit card numbers of certain WHR customers. To date, the only data elements our forensics expert has confirmed were accessed are names and credit card numbers.

The statement does not indicate precisely when the hack occurred or for how long the files were accessed.

As noted in the previous blog entry on this site, Wyndham tried to get these reports kept out of the public domain. They are not the only ones to have ever tried that, and I am pleased to see that at least some states are finding that breach reports are public records obtainable under their public records law. Here was Wyndham’s rationale/legal basis for requesting confidentiality:

At the outset, we would like to request confidential treatment for this letter and all future written and verbal correspondence related to this matter. In particular, we request that the information contained in this letter be exempt from disclosure as “information describing … [the] security of information technology infrastructure and systems.” ME. REV. STAT. ANN. tit. 1, § 402(3)(m).

If an entity provides a lot of actual detail about their security infrastructure and systems, I can understand seeking an exemption if disclosure of the details might increase their vulnerability to further attacks. But just admitting that you were hacked? I don’t think so….


Related:

  • Hacking Formula 1: Accessing Max Verstappen's passport and PII through FIA bugs
  • Protected health information of 462,000 members of Blue Cross Blue Shield of Montana involved in Conduent data breach
  • TX: Kaufman County Faces Cybersecurity Attack: Courthouse Computer Operations Disrupted
  • Hotel and Casino near Las Vegas Strip suffers data breach, documents say
  • Bombay High Court Orders Department of Telecommunications to Block Medusa Accounts After Generali Insurance Data Breach
  • KT Chief to Resign After Cybersecurity Breach Resolution
Category: Breach IncidentsBusiness SectorHackU.S.

Post navigation

← And yet 21 more breaches we didn’t know about
OR: Stolen computer contains participants’ personal 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

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

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.