HackingHospitalityHospitalityCustomer Data InvolvedIdentity (basic)LowContained

Baltimore Country Club

bd_0a6bc7cef384ae32 · schema v1 · pii pii-v1

Severity

Low

Discovered

Feb 1, 2025

Filed

Aug 26, 2025

To disclose

29 weeks

Affected

2state residents only

Linked

6 filings

Confidence

66%

Full breach record for Baltimore Country Club →

Baltimore Country Club, Inc. notified individuals of a data security incident discovered on February 1, 2025, involving unauthorized acquisition of files containing personal information. Notices were sent on August 26, 2025. The club engaged cybersecurity experts and offered identity protection services. Specific data types and total affected counts were not explicitly stated in the letter body.

J jump to incidentP pin to compareR raw source

Incident timeline

discovery → filing · 29 weeks / 206 days

Feb 1, 2025

Discovered

Aug 26, 2025

Filed

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

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Siteplaybd_47fd9f96a7c6ae5b2025-01-31 · +207dVerified by operator

Regulatory filings (4) · sorted by filing gap

New Hampshire State AGbd_1eebac0fd17c02ef2025-08-26Verified by operator
Indiana State AGbd_af8f8d2c96eb8ca42025-08-26Verified
Massachusetts State AGbd_6d164909906e605e2025-08-27 · +1dVerified by operator
Maryland State AGbd_1cafdd28e2d6c75b2025-03-06 · +173dVerified by operator

Name: Baltimore Country Club
norm: baltimore country club
Domain: bcc1898.com

Name: Baltimore Country Club
norm: baltimore country club
Domain: bcc1898.com
Industry: Hospitalityllm

Discovered: Feb 1, 2025
Materiality determined: —
Notification sent: Aug 26, 2025
Affected individuals: 2state-resident count only
Data types: Identity (basic)
Attack vector: Unauthorized Access
MITRE ATT&CK: T1078 Valid Accounts
Threat actor: External

During the incident: Engaged independent cybersecurity experts
Undertook a comprehensive review of those files
Offering complimentary identity protection services through IDX
Provided credit monitoring, dark web monitoring, and identity theft recovery services
Changes made: Implemented measures to enhance security and minimize the risk of a similar incident occurring in the future
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 29 weeks(206 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 ↗

Maryland State AGMar 6 · first

New Hampshire State AG+173d

Indiana State AG+173d

Montana State AG+173d · this page

Massachusetts State AG+174d

Pattern: first filing Mar 6 (MD), last Aug 27 (MA) — a 174-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/2025/09/Consumer-notification-letter-10.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Aug 26, 2025
Raw hash: 397e5fabcc6ba8223b156c8b18263c776527429fba1efeb21218f8c534d658f2

Linked disclosures

Ransomware claims (1)

Regulatory filings (4) · sorted by filing gap

Reporting entityBaltimore Country Club

Victim entityBaltimore Country Club

Incidentdiscovered Feb 1, 2025

Stated responseEngaged independent cybersecurity experts

Complianceclock not assessable

Extraction provenanceno artifact recorded

Source provenancedojmt.gov