HackingHospitalityHospitalityStolen CredentialsCapture Stored DataSupply Chain (3P Vendor)Customer Data InvolvedDelayed DiscoveryFinancial accountIdentity (basic)MediumContained

Preferred Hotels & Resorts

bd_0b11bd44018a4b03 · schema v1 · pii pii-v1

Severity

Medium

Discovered

Feb 14, 2018

Filed

Mar 2, 2018

To disclose

16 days

Affected

21,687state residents only

Linked

5 filings

Confidence

69%

Preferred Hotels & Resorts notified Washington AG of a third-party breach involving Sabre/SynXis. Unauthorized access via stolen credentials occurred June 2016–Nov 2017, affecting payment card data and guest PII for ~21,687 WA residents. Notification sent March 2018.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 623 days

discovery → filing · 16 days

Jun 1, 2016

Begins

Feb 14, 2018

Discovered

Mar 2, 2018

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

New Hampshire State AGbd_24e0474a5c4393b22018-03-02Verified
Oregon State AGbd_92af1cd4dff3ae962018-03-02Verified
California State AGbd_b9283f1173df061d2018-03-02Verified
Massachusetts State AGbd_34823ecac168feff2018-03-09 · +7dVerified

Name: Preferred Hotels & Resorts
norm: preferred hotels

Name: Preferred Hotels & Resorts
norm: preferred hotels
Industry: Hospitalityllm

Discovered: Feb 14, 2018
Breach occurred: Jun 1, 2016 – Nov 30, 2017
Undetected for: 623 daysoccurrence → discovery
Materiality determined: —
Notification sent: Mar 5, 2018
Affected individuals: 21,687state-resident count only
Data types: Financial accountIdentity (basic)
Data elements: NameFinancial account number
WA-stated cause: Cyberattack
WA-stated duration: lifecycle 500+dexposure 500+d
WA-stated discovery: Found after the fact
Attack vector: Third-Party / Supply Chain
MITRE ATT&CK: T1078 Valid AccountsT1119 Automated Collection
Threat actor: ExternalFinancial
Regulator citations: Vendor notified law enforcement and payment card brands
Third party: via Sabre/SynXis
Initial access: valid_credentials

During the incident: Initiated an investigation into the incident
Communicated extensively with the vendor
Continuing to take actions, in cooperation with Sabre, to improve the security and protection of all reservations information
Enhance all systems to help prevent this type of incident from recurring
Changes made: Vendor enhanced the security around its access credentials
Vendor enhanced the monitoring of system activity
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 16 days(16 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 ↗

New Hampshire State AGMar 2 · first

Oregon State AGMar 2 · first

California State AGMar 2 · first

Washington State AGMar 2 · first · this page

Massachusetts State AG+7d

Pattern: first filing Mar 2 (NH), last Mar 9 (MA) — a 7-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://agportal-s3bucket.s3.amazonaws.com/databreach/BreachM9769.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Mar 2, 2018
Raw hash: 128b0770b537ba022c9497e25af76e46802a7954aafa406aab3aeb415accaebe

Linked disclosures

Regulatory filings (4) · sorted by filing gap

Reporting entityPreferred Hotels & Resorts

Victim entityPreferred Hotels & Resorts

Incidentdiscovered Feb 14, 2018

Stated responseInitiated an investigation into the incident

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceagportal-s3bucket.s3.amazonaws.com