Confirmed breach. Intrusion Aug 22, 2025, discovered Aug 22, 2025 — the first regulatory filing landed 35 days later. 19,696 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksLeak gap⏱ Leak >30dWashington⏱ WA AG >30dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
19,696
Data types
—
Jurisdictions
2
IN WA
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Aug 22, 2025
When the intrusion reportedly occurred, per the linked filings
Breach discoveredAG web form
Aug 22, 2025
Reported by WASHINGTON AG filing
35 days
🏎️Indiana State AGFirst filinglinked via multistate filing link · 100%
Georgetown Brewing Company reported a data breach to the Indiana Attorney General. The breach occurred on 2025-08-22 and was reported on 2025-09-26. 1 Indiana residents were affected. 19,696 individuals affected in total.
Georgetown Brewing Company, a business sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2025-08-22 and filed notice on 2025-09-26. 19,143 Washington residents were affected. 35 days elapsed between awareness and notification. 0 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 19,143
WA AG >30d
About this clustering
DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.