HackingHospitalityHospitalitySkimmerTargetedCustomer Data InvolvedFinancial accountIdentity (basic)LowContained

HYATT HOTELS CORPORATION

bd_7c8b3aa1bbff52c4 · schema v1 · pii pii-v1

Severity

Low

Discovered

Jul 7, 2017

Filed

Oct 12, 2017

To disclose

14 weeks

Affected

640state residents only

Linked

6 filings

Confidence

71%

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

Hyatt Hotels Corporation notified the Washington AG of a cyberattack involving skimmers at hotel front desks. Unauthorized access to payment card data (names, numbers, CVVs) occurred between March 18 and July 2, 2017. Hyatt discovered the incident on July 7, 2017, and began notifying affected individuals, including 640 Washington residents, on October 12, 2017.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 111 days

discovery → filing · 14 weeks / 97 days

Mar 18, 2017

Begins

Jul 7, 2017

Discovered

Oct 12, 2017

Filed

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

Linked disclosures

Why this link?

Regulatory filings (5) · sorted by filing gap

Montana State AGbd_0870ccb3554d9ca82017-10-12Candidate
California State AGbd_278fdf50e5a5cf702017-10-12Verified
Massachusetts State AGbd_367cd7b53d3b35da2017-10-12Verified
Oregon State AGbd_77367de9ad6997d42017-10-12Verified

Show 1 more filing ↓

New Hampshire State AGbd_bfd81870eddbe2202017-10-12Verified

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

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

Discovered: Jul 7, 2017
Breach occurred: Mar 18, 2017 – Jul 2, 2017
Undetected for: 111 daysoccurrence → discovery
Materiality determined: —
Notification sent: Oct 12, 2017
Affected individuals: 640state-resident count only
Data types: Financial accountIdentity (basic)
Data elements: NameFinancial account number
WA-stated cause: Cyberattack
WA-stated duration: lifecycle 100-199dexposure 100-199d
WA-stated discovery: Found after the fact
Attack vector: Unknown
MITRE ATT&CK: T1052 Exfiltration Over Physical Medium
Threat actor: ExternalFinancial
Regulator citations: Notified Attorney General Bob Ferguson
Initial access: external_remote_services

During the incident: Launched a comprehensive investigation
Engaging leading third-party experts, payment card networks and authorities
Set up a call center staffed with dedicated support specialists
Changes made: Implemented enhanced cybersecurity measures and additional layers of defense
Continuing to evaluate its security measures and processes to identify where additional improvements are necessary
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 14 weeks(97 days from discovery to filing)
Compliance flags: — (clock not assessable for this source)

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 6 filings · 6 states

View merged incident ↗

Montana State AGOct 12 · first

California State AGOct 12 · first

Massachusetts State AGOct 12 · first

Oregon State AGOct 12 · first

New Hampshire State AGOct 12 · first

Washington State AGOct 12 · first · this page

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://agportal-s3bucket.s3.amazonaws.com/databreach/BreachM10499.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Oct 12, 2017
Raw hash: ca656a6c9be4e6a4546022e9b5f7b8aeec8151533a281d7e495a815e1e7dc6ea

Linked disclosures

Regulatory filings (5) · sorted by filing gap

Reporting entityHYATT HOTELS CORPORATION

Victim entityHYATT HOTELS CORPORATION

Incidentdiscovered Jul 7, 2017

Stated responseLaunched a comprehensive investigation

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceagportal-s3bucket.s3.amazonaws.com