MalwareHospitalityHospitalityRansomwareData ExfiltratedCustomer Data InvolvedPCIFinancial accountIdentity (basic)LowContained

HYATT HOTELS CORPORATION

bd_c0076be75d103666 · schema v1 · pii pii-v1

Severity

Low

Discovered

—

Filed

Jan 19, 2016

To disclose

—

Affected

5state residents only

Linked

5 filings

Confidence

65%

Full breach record for HYATT HOTELS CORPORATION →3 incidents on file

Hyatt Hotels Corporation disclosed a payment card incident involving malware that collected cardholder data (name, number, expiration, verification code) from onsite payment processing systems at certain locations. The unauthorized access occurred between July 30, 2015, and December 8, 2015. Hyatt engaged third-party security experts, notified law enforcement, and offered one year of fraud detection services to affected customers.

J jump to incidentP pin to compareR raw source

Incident timeline

Jul 30, 2015

Begins

Jan 19, 2016

Filed

This filing is one of 5 filings about the same incident.View merged incident

Linked disclosures

Why this link?

Regulatory filings (4) · sorted by filing gap

Massachusetts State AGbd_bd44d7ae4cd4995f2016-01-15 · +4dVerified
Washington State AGbd_02b089e878b47abd2016-01-14 · +5dCandidate
California State AGbd_bc7429716d81c1022016-01-14 · +5dVerified
Montana State AGbd_e41f481fb05b9df92016-01-14 · +5dVerified

Name: HYATT HOTELS CORPORATION
norm: hyatt hotels
Domain: hyatt.com

Name: HYATT HOTELS CORPORATION
norm: hyatt hotels
Domain: hyatt.com
Industry: Hospitalityllm

Discovered: —
Breach occurred: Jul 30, 2015 – Dec 8, 2015
Materiality determined: —
Notification sent: Jan 14, 2016
Affected individuals: 5state-resident count only
Data types: PCIFinancial accountIdentity (basic)
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1052 Exfiltration Over Physical Medium
Threat actor: ExternalFinancial
Initial access: external_remote_services

During the incident: Worked with leading third-party cyber security experts to resolve the issue and strengthen the security of its systems
Notified law enforcement and the payment card networks
Changes made: Strengthened the security of its systems
Source: Quoted from the filing itself, not independently verified.

Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 5 filings · 5 states

View merged incident ↗

Washington State AGJan 14 · first

California State AGJan 14 · first

Montana State AGJan 14 · first

Massachusetts State AG+1d

South Carolina State AG+5d · this page

Pattern: first filing Jan 14 (WA), last Jan 19 (SC) — a 5-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?

Evidence ladder

Leak-site claim

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filingThis record

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Source URL: https://consumer.sc.gov/sites/consumer/files/Documents/Business%20Resources%20Laws/Related%20Laws/Breaches/2016/HyattHotelsCorporation.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jan 19, 2016
Raw hash: 2510dba1821edde94192bcfb935964179b44afd897b37e85896352b3b7f806b5

Linked disclosures

Regulatory filings (4) · sorted by filing gap

Reporting entityHYATT HOTELS CORPORATION

Victim entityHYATT HOTELS CORPORATION

IncidentRansomware

Stated responseWorked with leading third-party cyber security experts to resolve the issue and strengthen the security of its systems

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceconsumer.sc.gov