MalwareHospitalityHospitalityRansomwareData ExfiltratedCustomer Data InvolvedPCIFinancial accountIdentity (basic)LowResolved

HYATT HOTELS CORPORATION

bd_e41f481fb05b9df9 · schema v1 · pii pii-v1

Severity

Low

Discovered

Aug 13, 2015

Filed

Jan 14, 2016

To disclose

22 weeks

Affected

1state residents only

Linked

5 filings

Confidence

64%

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

Hyatt Hotels Corporation completed an investigation into a payment card incident involving malware that collected cardholder data from onsite payment processing systems at certain locations between July 30, 2015, and December 8, 2015. Hyatt engaged third-party experts, notified law enforcement and card networks, and offered one year of fraud protection services to affected customers.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 14 days

discovery → filing · 22 weeks / 154 days

Jul 30, 2015

Begins

Aug 13, 2015

Discovered

Jan 14, 2016

Filed

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

Linked disclosures

Why this link?

Regulatory filings (4) · sorted by filing gap

Washington State AGbd_02b089e878b47abd2016-01-14Candidate
California State AGbd_bc7429716d81c1022016-01-14Verified
Massachusetts State AGbd_bd44d7ae4cd4995f2016-01-15 · +1dVerified
South Carolina State AGbd_c0076be75d1036662016-01-19 · +5dVerified

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

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

Discovered: Aug 13, 2015
Breach occurred: Jul 30, 2015 – Dec 8, 2015
Undetected for: 14 daysoccurrence → discovery
Materiality determined: —
Notification sent: Jan 14, 2016
Affected individuals: 1state-resident count only
Data types: PCIFinancial accountIdentity (basic)
Attack vector: Unknown
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1052 Exfiltration Over Physical Medium
Threat actor: ExternalFinancial
Regulator citations: Notified law enforcement
Initial access: external_remote_services

During the incident: Worked with leading third-party cyber security experts to resolve the issue
Strengthened the security of its systems
Notified law enforcement
Notified the payment card networks
Mailed letters to customers for whom Hyatt has a mailing address
Sent emails to customers for whom Hyatt has an email address
Arranged for CSID to provide one year of CSID’s Protector services to affected customers at no cost
Changes made: Strengthened the security of its systems
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 22 weeks(154 days from discovery to filing)
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 · this page

Massachusetts State AG+1d

South Carolina State AG+5d

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://dojmt.gov/wp-content/uploads/Hyatt-Hotel-Corporation.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jan 14, 2016
Raw hash: 48928d33694f859031fbb028140b0b2f330b8c602497839fb15bc97837485184

Linked disclosures

Regulatory filings (4) · sorted by filing gap

Reporting entityHYATT HOTELS CORPORATION

Victim entityHYATT HOTELS CORPORATION

Incidentdiscovered Aug 13, 2015

Stated responseWorked with leading third-party cyber security experts to resolve the issue

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov