UnknownGovernment IDMedium

McMenamins, Inc.

bd_c09f19d8ba46b5fa · schema v1 · pii pii-v1

Severity

Medium

Discovered

—

Filed

Jan 18, 2022

To disclose

—

Affected

11state residents only

Linked

7 filings

Confidence

95%

Full breach record for McMenamins, Inc. →

McMenamins, Inc. reported a data breach to the Massachusetts Office of Consumer Affairs and Business Regulation. The breach was reported on 2022-01-18. 11 Massachusetts residents were affected. The report records the breach type as electronic.

J jump to incidentP pin to compareR raw source

Massachusetts clock✓ MA credit monitoring due

⚠ no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.

Incident timeline — partial

? — ?

Breach window unknown

Jan 18, 2022

Filed

—

Corroborated · see linked filings

Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.

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

Linked disclosures

Why this link?

Ransomware claims (1)

Leak Sitecontibd_d9892f7c34e2cea52021-12-21 · +28dVerified by operator

Regulatory filings (5) · sorted by filing gap

New Hampshire State AGbd_40847924a834e0f42022-01-18Verified
Maine State AGbd_feba65f7cb20750a2022-01-18Verified
Washington State AGbd_48a7a67a3ff6841c2021-12-30 · +19dCandidate
Oregon State AGbd_7f15c8a5259550dd2021-12-30 · +19dVerified

Show 1 more filing ↓up to 19d gap

Indiana State AGbd_893688775c71c6d42021-12-30 · +19dVerified

Name: McMenamins, Inc.
norm: mcmenamins

Name: McMenamins, Inc.
norm: mcmenamins

Discovered: —
Materiality determined: —
Notification sent: —
Affected individuals: 11state-resident count only
Data types: Government ID
Data elements: Social Security number
Stated not affected: Financial account numberDriver's licence numberPayment card number
The filing states these were not involved. Categories absent from both lists were not addressed either way.
Attack vector: Unknown

Compliance flags: MA credit monitoring due
Discovery-date grounding: no discovery dateNo discovery date was extracted, so no notification clock can be evaluated.

Status: No extraction artifact recorded for this disclosure.

Filing propagation · 6 filings · 6 states

View merged incident ↗

Washington State AGDec 30 · first

Oregon State AGDec 30 · first

Indiana State AGDec 30 · first

New Hampshire State AG+19d

Maine State AG+19d

Massachusetts State AG+19d · this page

Pattern: first filing Dec 30 (WA), last Jan 18 (MA) — a 19-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://www.mass.gov/doc/data-breach-report-2022/download
DisclosureLens links to the originating regulator URL — full filing bodies are not redistributed from public surfaces (§4.5).
Filed at: Jan 18, 2022
Raw hash: 104376d814a459c6e33cb2078383088fd5fb2d7d6a25191a66c59164b0c774f9

Linked disclosures

Ransomware claims (1)

Regulatory filings (5) · sorted by filing gap

Reporting entityMcMenamins, Inc.

Victim entityMcMenamins, Inc.

IncidentUnknown

ComplianceMA credit monitoring due

Extraction provenanceno artifact recorded

Source provenancewww.mass.gov