MalwareHospitalityHospitalityRansomwareData ExfiltratedRansom DemandedFinancial accountIdentity (basic)Government IDHighContained

Georgetown Brewing Company

bd_d1ceb3c9b2dd60da · schema v1 · pii pii-v1

Severity

High

Discovered

Aug 22, 2025

Filed

Sep 26, 2025

To disclose

5 weeks

Affected

19,143state residents only

Linked

7 filings

Confidence

70%

Full breach record for Georgetown Brewing Company →2 incidents on file

Georgetown Brewing Company reported a ransomware incident on August 22, 2025, affecting 19,143 Washington residents. The breach exposed names and driver's license numbers. The company notified law enforcement and offered IDX identity protection services.

J jump to incidentP pin to compareR raw source

Leak gap clock⏱ Leak >30d5 weeks discovery → filing

⚠ occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.

Incident timeline

discovery → filing · 5 weeks / 35 days

Aug 22, 2025

Begins

Aug 22, 2025

Discovered

Sep 26, 2025

Filed

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

Linked disclosures

Why this link?

Regulatory filings (6) · sorted by filing gap

Massachusetts State AGbd_1ef919bdc0a408392025-09-26Verified
Nebraska State AGbd_4401b669b64ed4c02025-09-26Verified
Maine State AGbd_44441ed00e966a822025-09-26Verified
Indiana State AGbd_507654b336c26f6a2025-09-26Verified

Show 2 more filings ↓

Vermont State AGbd_c62af42c4d23d1a22025-09-26Verified
Montana State AGbd_ccef8b961699fbfe2025-09-26Candidate

Name: Georgetown Brewing Company
norm: georgetown brewing
Domain: georgetownbeer.com

Name: Georgetown Brewing Company
norm: georgetown brewing
Domain: georgetownbeer.com
Industry: Hospitalityllm

Discovered: Aug 22, 2025
Breach occurred: Aug 22, 2025
Undetected for: 0 daysoccurrence → discovery
Materiality determined: —
Notification sent: Sep 26, 2025
Affected individuals: 19,143state-resident count only
Data types: Identity (basic)Government ID
Data elements: NameSocial Security numberDriver's licence numberFinancial account numberDate of birth
WA-stated cause: Cyberattack
WA-stated duration: lifecycle 0dexposure 0d
WA-stated discovery: Found while ongoingContained same day
Attack vector: Ransomware
MITRE ATT&CK: T1486 Data Encrypted for ImpactT1041 Exfiltration Over C2 Channel
Threat actor: ExternalFinancial
Regulator citations: Reported to Washington Attorney General

During the incident: Reported this incident to law enforcement
Offering identity theft protection services through IDX
Changes made: Taking steps to implement additional safeguards
Review policies and procedures relating to data privacy and security
Source: Quoted from the filing itself, not independently verified.

Time to disclose: 5 weeks(35 days from discovery to filing)
Compliance flags: Leak >30dWA AG >30d
Discovery-date grounding: occurrence dateThe stored discovery date equals the breach OCCURRENCE date. Detection is normally later, so this OVERSTATES the delay — a 'late' verdict here may not be real.

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 7 filings · 7 states

View merged incident ↗

Massachusetts State AGSep 26 · first

Nebraska State AGSep 26 · first

Maine State AGSep 26 · first

Indiana State AGSep 26 · first

Vermont State AGSep 26 · first

Montana State AGSep 26 · first

Washington State AGSep 26 · first · this page

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/BreachA34771.pdf
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Sep 26, 2025
Raw hash: ad395a37bc81f75835bd2d60e84ef9aa4eee78a838af15024bfe06162fd740bd

Linked disclosures

Regulatory filings (6) · sorted by filing gap

Reporting entityGeorgetown Brewing Company

Victim entityGeorgetown Brewing Company

Incidentdiscovered Aug 22, 2025

Stated responseReported this incident to law enforcement

ComplianceLeak >30d

Extraction provenanceno artifact recorded

Source provenanceagportal-s3bucket.s3.amazonaws.com