HackingHospitalityHospitalityStolen CredentialsSupply Chain (3P Vendor)Customer Data InvolvedDelayed DiscoveryIdentity (basic)Financial accountLowContained

Drury Hotels Company, LLC

bd_f0f15ceb228b6bfa · schema v1 · pii pii-v1

Severity

Low

Discovered

Mar 26, 2019

Filed

May 24, 2019

To disclose

8 weeks

Affected

Not disclosed

Linked

8 filings

Confidence

69%

Full breach record for Drury Hotels Company, LLC →2 incidents on file

Drury Hotels Company, LLC notified the Washington AG of a third-party vendor breach affecting payment card data (names, card numbers, CVV) for Washington residents. Unauthorized access occurred Dec 29, 2017 – Mar 13, 2019. Drury was notified by the vendor on Mar 26, 2019. Notifications mailed starting May 30, 2019. Exact count of affected Washington residents unknown.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 452 days

discovery → filing · 8 weeks / 59 days

Dec 29, 2017

Begins

Mar 26, 2019

Discovered

May 24, 2019

Filed

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

Linked disclosures

Why this link?

Regulatory filings (7) · sorted by filing gap

Massachusetts State AGbd_6eb94101ffe1dab72019-05-24Verified
Delaware State AGbd_6fdf9670ce0a04b92019-05-24Verified
Oregon State AGbd_8cff209251c26c892019-05-24Candidate
South Carolina State AGbd_9fe18ee36ef756992019-05-28 · +4dVerified

Show 3 more filings ↓up to 7d gap

New Hampshire State AGbd_f4ff65a69e351e422019-05-28 · +4dVerified
Montana State AGbd_6bcb0a38a95b2df62019-05-30 · +6dVerified
New Hampshire State AGbd_ac91d65a4d1937b82019-05-31 · +7dVerified

Name: Drury Hotels Company, LLC
norm: drury hotels

Name: Drury Hotels Company, LLC
norm: drury hotels
Industry: Hospitalityllm

Discovered: Mar 26, 2019
Breach occurred: Dec 29, 2017 – Mar 13, 2019
Undetected for: 452 daysoccurrence → discovery
Materiality determined: —
Notification sent: May 30, 2019
Affected individuals: Not disclosed
Data types: Identity (basic)Financial account
Data elements: NameFinancial account number
WA-stated cause: Cyberattack
WA-stated duration: lifecycle 400-499dexposure 400-499d
WA-stated discovery: Found after the fact
Attack vector: Third-Party / Supply Chain
MITRE ATT&CK: T1195 Supply Chain CompromiseT1530 Data from Cloud Storage Object
Threat actor: External
Regulator citations: Notified Washington Attorney General Consumer Protection Division
Initial access: supply_chain

During the incident: Worked closely with Vendor to get updates on its investigation
Mailed notification letters via United States Postal Service First-Class Mail to Washington residents
Issued a press release
Posted a statement on its website
Established a dedicated call center
Changes made: Working with Vendor to identify security enhancements it is implementing
Source: Quoted from the filing itself, not independently verified.

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

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 8 filings · 7 states

View merged incident ↗

Massachusetts State AGMay 24 · first

Delaware State AGMay 24 · first

Oregon State AGMay 24 · first

Washington State AGMay 24 · first · this page

South Carolina State AG+4d

New Hampshire State AG+4d

Montana State AG+6d

New Hampshire State AG+7d

Pattern: first filing May 24 (MA), last May 31 (NH) — 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/BreachM10634.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: May 24, 2019
Raw hash: 6c5d791886c315948610504d6cfd9167d456a6fac07c579eff4656515b0b416c

Linked disclosures

Regulatory filings (7) · sorted by filing gap

Reporting entityDrury Hotels Company, LLC

Victim entityDrury Hotels Company, LLC

Incidentdiscovered Mar 26, 2019

Stated responseWorked closely with Vendor to get updates on its investigation

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenanceagportal-s3bucket.s3.amazonaws.com