DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed11 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 11 filings

Monro, Inc. — November 2024 breach

Clustered 11 filings across 11 jurisdictions · filing window Mar 1, 2025 → Mar 27, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

112,458

First → last filing

Mar 1, 2025 → Mar 27, 2025

Merge confidence

100%

incident inc_27c59f0be2734340 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. Intrusion Nov 1, 2024–Nov 30, 2024, discovered Nov 1, 2024 — the first regulatory filing landed 120 days later (flagged late). 112,458 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Identity (basic), and 3 more. Notifications rolled out on a 26-day schedule across 11 filings beginning Mar 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
120days

Discovered → first regulatory filing

Discovery variance
28days

Range of discovered_at dates across filings

Filing span
26days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksMaryland✗ MD AG >90dVermont✗ VT AG >45 bdayMaine✗ ME AG >90d · 116dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 1, 2024breach begins
Nov 1, 2024discovered · members disagree
notification delay · 120 days
Mar 1, 2025first filing
Mar 27, 2025most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. MAR 1IL AGIL AG noticefirst filing · no count statedday 0
  2. MAR 20MD AGMD AG notice8,329 MD residents+19d
  3. MAR 21CA AGCA AG noticeno count stated+20d
  4. MAR 21IN AGIN AG noticestates nationwide total 112,458+20d
  5. MAR 21DE AGDE AG noticeno count stated+20d
  6. MAR 24NH AGNH AG notice2,643 NH residents+23d
  7. MAR 25VT AGVT AG noticeno count stated+24d
  8. MAR 25MA AGMA AG notice5,026 MA residents+24d
  9. MAR 25ME AGME AG noticestates nationwide total 112,458+24d
  10. MAR 26SC AGSC AG notice2,821 SC residents+25d
  11. MAR 27RI AGRI AG noticemost recent · 975 RI residents+26d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 29, 2024
MD AG
Discovered
Nov 1, 2024DE AG + VT AG + SC AGNov 21, 2024CA AGNov 29, 2024IL AG + MD AG + NH AG +2filings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PII
IL AG + MD AG + CA AG +7
Attack vector
Unauthorized Access
MD AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

112,458

Sum of filed state slices

25,634· 22.8% of stated

77% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US112,458
MD8,329
MA5,026
IN4,406
SC2,821
NH2,643
ME1,434
RI975

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing11 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

26 days

Cadence

~1 / 2.6d

vs. multi-state median

3.3× slower

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. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.