McMenamins, Inc.
bd_7f15c8a5259550dd · schema v1 · pii pii-v1
Full breach record for McMenamins, Inc. →McMenamins, Inc. reported a data breach to the Oregon Attorney General. The breach was reported on 2021-12-30. The breach was discovered on 1/1/0001. 20,504 individuals were affected.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Dec 30, 2021
Filed
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Sitecontibd_d9892f7c34e2cea52021-12-21 · +9dVerified by operator
Regulatory filings (5) · sorted by filing gap
- Washington State AGbd_48a7a67a3ff6841c2021-12-30Candidate
- Indiana State AGbd_893688775c71c6d42021-12-30Verified
- New Hampshire State AGbd_40847924a834e0f42022-01-18 · +19dVerified
- Massachusetts State AGbd_c09f19d8ba46b5fa2022-01-18 · +19dVerified by operator
Show 1 more filing ↓Show fewer ↑up to 19d gap
- Maine State AGbd_feba65f7cb20750a2022-01-18 · +19dVerified
Filing propagation · 6 filings · 6 states
View merged incident ↗Pattern: first filing Dec 30 (WA), last Jan 18 (ME) — a 19-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
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.