By Manny Fernandez

February 12, 2017

Data Breaches – February 2017

Below are the breaches for February 2017 that were made public. If you have accounts with any of there services/companies make sure you change your passwords and ensure you are monitoring your credit for anomalies.

ORGANIZATION: Michigan Government
DATE OF BREACH: October 10, 2016 – January 30, 2017
DATE MADE PUBLIC: February 3, 2017
RECORDS AFFECTED: 1.87 Million

DATA COMPROMISED:
A software update performed by the vendor supporting the unemployment benefits computer system introduced a vulnerability that allowed authorized users of the Michigan Data Automated System (MiDAS) to access personal information they were not authorized to view. The authorized users who potentially had access only include employers and other human resources professionals, not unemployment claimants or the general public. Compromised information includes names, Social Security numbers and wage information.

—————————————————————————
ORGANIZATION: CD Projekt Red
DATE OF BREACH: March 2016
DATE MADE PUBLIC: January 31, 2017
RECORDS AFFECTED: 1.8 Million

DATA COMPROMISED:
Polish game development studio CD Projekt RED has had more than 1.8 million user credentials stolen from its online forum. The studio, which is famous for developing the highly successful Witcher franchise, was breached when hackers targeted its online forum, leading to a leak of usernames, passwords and email addresses.
—————————————————————————
ORGANIZATION: Arby’s
DATE OF BREACH: October 25, 2016 – January 19, 2017
DATE MADE PUBLIC: February 9, 2017
RECORDS AFFECTED: Unknown

DATA COMPROMISED:
Hackers have stolen customer credit card information from an unknown number of Arby’s restaurants. Arby’s said the breach involved malware placed on payment systems inside corporate stores, and that Arby’s franchised restaurant locations were not impacted. Arby’s is working with law enforcement and computer security companies to investigate and the malware has since been removed from affected systems.
—————————————————————————
ORGANIZATION: IHG Hotels
DATE OF BREACH: August – December, 2016
DATE MADE PUBLIC: February 3, 2017
RECORDS AFFECTED: 12 IHG Properties

DATA COMPROMISED:
Findings show that malware was installed on servers that processed payment cards used at restaurants and bars of 12 IHG managed properties. Cards used at the front desk of these properties were not affected. The malware searched for track data (cardholder name, card number, expiration date, and internal verification code) read from the magnetic stripe of a payment card as it was being routed through the affected server. A list of the affected restaurants and bars, along with the specific time frames for each can be found here. An investigation of other properties in the Americas region is ongoing.
—————————————————————————
ORGANIZATION: VICI Marketing LLC
DATE OF BREACH: Unknown
DATE MADE PUBLIC: January 27, 2017
RECORDS AFFECTED: 17,649

DATA COMPROMISED:
The telemarketing firm leaked online more than 17,000 calls in which customers disclosed their credit card information to its representatives. In the audio recordings, customers gave out their names, physical addresses, phone number, credit card number, CV numbers, and more. Additionally, a research team found 375,368 “cold calls” that might also contain customers’ personal information.
—————————————————————————
ORGANIZATION: Verity Health
DATE OF BREACH: October 2015 – January 2017
DATE MADE PUBLIC: February 6, 2017
RECORDS AFFECTED: 9,000

DATA COMPROMISED:
About 9,000 Verity Health patients had their personal data compromised after an unauthorized entry was discovered in the health system’s network. The information dated between 2010 and 2014 included patient names, birth date, medical record numbers, address, email, phone numbers and the last four digits of their credit cards. No Social Security numbers were exposed.

Recent posts

  • There are many options when troubleshooting in FortiGate firewalls. ... Full Story

  • Have you ever had an IPS signature that continues... Full Story

  • Use case:  Customer has a Split Tunnel Enabled but... Full Story