Georgetown Brewing Company
bd_e7b83d97438da500 · schema v1 · pii pii-v1
Full breach record for Georgetown Brewing Company →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group INC Ransom on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
Georgetown Brewing Company is an independently owned craft brewery located in Seattle, known for its flagship beer, Mannys Pale Ale. The brewery transitioned from draft-only production to canning select beers and offers pints in its tasting room alongside kegs, growlers, and cans for customers to take home. Their focus remains on brewing high-quality, flavorful beer, with a lively atmosphere that encourages visitors to enjoy their offerings on-site or at local bars. Intended clients include craft beer enthusiasts and patrons looking to experience unique local brews.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Aug 22, 2025
Claim posted
—
Corroborated · see linked filings
This record's own dates cannot anchor compliance clocks; see the linked filings.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (7) · sorted by filing gap
- Massachusetts State AGbd_1ef919bdc0a408392025-09-26 · +35dVerified
- Nebraska State AGbd_4401b669b64ed4c02025-09-26 · +35dVerified
- Maine State AGbd_44441ed00e966a822025-09-26 · +35dVerified by operator
- Indiana State AGbd_507654b336c26f6a2025-09-26 · +35dVerified
Show 3 more filings ↓Show fewer ↑up to 35d gap
- Vermont State AGbd_c62af42c4d23d1a22025-09-26 · +35dVerified by operator
- Montana State AGbd_ccef8b961699fbfe2025-09-26 · +35dVerified by operator
- Washington State AGbd_d1ceb3c9b2dd60da2025-09-26 · +35dVerified by operator
Filing propagation · 7 filings · 7 states
View merged incident ↗Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.