Social EngineeringHospitalityHospitalityPhishingCustomer Data InvolvedDelayed DiscoveryPIIIdentity (basic)LowContained

Aimbridge Hospitality Holdings, LLC

bd_bdeac05efe79abd2 · schema v1 · pii pii-v1

Severity

Low

Discovered

Sep 14, 2018

Filed

Dec 31, 2018

To disclose

15 weeks

Affected

841state residents only

Linked

6 filings

Confidence

65%

Full breach record for Aimbridge Hospitality Holdings, LLC →3 incidents on file

Aimbridge Hospitality Holdings, LLC notified individuals of a phishing incident resulting in unauthorized access to employee email accounts between June 7 and September 24, 2018. The company discovered the incident on September 14, 2018. Affected data included names and other personal information. The company engaged forensic experts, reset passwords, and provided credit monitoring services.

J jump to incidentP pin to compareR raw source

Incident timeline

undetected · 99 days

discovery → filing · 15 weeks / 108 days

Jun 7, 2018

Begins

Sep 14, 2018

Discovered

Dec 31, 2018

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

Massachusetts State AGbd_9530f0e8c007b1d22018-12-31Verified
Oregon State AGbd_a7120229d278b1422018-12-31Candidate
Washington State AGbd_f19008c3ce0568512018-12-31Verified
California State AGbd_e48eb334deda60f62019-01-02 · +2dVerified

Show 1 more filing ↓up to 3d gap

New Hampshire State AGbd_91c48fafabf546932019-01-03 · +3dVerified

Name: Aimbridge Hospitality Holdings, LLC
norm: aimbridge hospitality

Name: Aimbridge Hospitality Holdings, LLC
norm: aimbridge hospitality
Industry: Hospitalityllm

Discovered: Sep 14, 2018
Breach occurred: Jun 7, 2018 – Sep 24, 2018
Undetected for: 99 daysoccurrence → discovery
Materiality determined: —
Notification sent: Dec 26, 2018
Affected individuals: 841state-resident count only
Data types: PIIIdentity (basic)
Attack vector: Phishing
MITRE ATT&CK: T1566.002 Spearphishing LinkT1078 Valid Accounts
Threat actor: ExternalFinancial
Initial access: phishing_link

During the incident: Launched an internal investigation
Engaged computer forensics experts
Reset passwords for the affected email accounts
Implemented increased security measures for email account access
Conducted additional employee training
Reviewing our policies and procedures relating to data security
Arranged for you to enroll, at no cost to you, in an online credit monitoring service
Changes made: Implemented increased security measures for email account access
Conducted additional employee training
Reviewing our policies and procedures relating to data security
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 15 weeks(108 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 ↗

Massachusetts State AGDec 31 · first

Oregon State AGDec 31 · first

Washington State AGDec 31 · first

Montana State AGDec 31 · first · this page

California State AG+2d

New Hampshire State AG+3d

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/Aimbridge-Hospitality-Holdings-LLC-1.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Dec 31, 2018
Raw hash: cc469b9f9a2104904b1ddf99a7beb8c7e1ee3131f478c0675945bc17ca11eff4

Linked disclosures

Regulatory filings (5) · sorted by filing gap

Reporting entityAimbridge Hospitality Holdings, LLC

Victim entityAimbridge Hospitality Holdings, LLC

Incidentdiscovered Sep 14, 2018

Stated responseLaunched an internal investigation

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov