MalwareHospitalityHospitalityRansomwareData ExfiltratedTargetedFinancial accountPIILowResolved

Noble House Hotels & Resorts

bd_85855e0b7f205d61 · schema v1 · pii pii-v1

Severity

Low

Discovered

—

Filed

Nov 13, 2015

To disclose

—

Affected

165state residents only

Linked

6 filings

Confidence

65%

Full breach record for Noble House Hotels & Resorts →3 incidents on file

Noble House Hotels and Resorts notified guests of a malware incident affecting payment processing systems at multiple properties from late 2014 to August 2015. Compromised data included magnetic stripe information (card numbers, CVVs). The company notified the FBI and engaged a security firm. No specific count of affected individuals was provided.

J jump to incidentP pin to compareR raw source

Incident timeline

Dec 29, 2014

Begins

Nov 13, 2015

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

Washington State AGbd_d4d28c3e1db2a0602015-11-13Verified
California State AGbd_e2f8c5fd4eb0c17c2015-11-13Candidate
Massachusetts State AGbd_6c50c7685a73af7a2015-10-23 · +21dVerified
California State AGbd_86c0d979209ba1372015-10-22 · +22dCandidate

Show 1 more filing ↓up to 22d gap

Montana State AGbd_c3fda7e524927e3b2015-10-22 · +22dVerified

Name: Noble House Hotels & Resorts
norm: noble house hotels resorts

Name: Noble House Hotels & Resorts
norm: noble house hotels resorts
Industry: Hospitalityllm

Discovered: —
Breach occurred: Dec 29, 2014 – Aug 11, 2015
Materiality determined: —
Notification sent: Nov 12, 2015
Affected individuals: 165state-resident count only
Data types: Financial accountPII
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1052 Exfiltration Over Physical Medium
Threat actor: ExternalFinancial
Regulator citations: Notified the FBI

During the incident: Notified the FBI regarding the incident
Engaged a computer security firm to examine our payment processing system
Working with the computer security firm to review our security measures
Ensured that this issue has been fully remediated
Changes made: Reviewing security measures with computer security firm
Enhancing security measures
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 · 6 filings · 4 states

View merged incident ↗

California State AGOct 22 · first

Montana State AGOct 22 · first

Massachusetts State AG+1d

Washington State AG+22d

California State AG+22d

Montana State AG+22d · this page

Pattern: first filing Oct 22 (CA), last Nov 13 (MT) — a 22-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/Noble-House-Hotels-and-Resorts2.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Nov 13, 2015
Raw hash: 97f24faeefb67e58d847a171705e81f5e0a37a975362024b80f48b9074119203

Linked disclosures

Regulatory filings (5) · sorted by filing gap

Reporting entityNoble House Hotels & Resorts

Victim entityNoble House Hotels & Resorts

IncidentRansomware

Stated responseNotified the FBI regarding the incident

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov