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

CHIPOTLE MEXICAN GRILL, INC. — October 2025 breach

Clustered 6 filings across 6 jurisdictions · filed Dec 23, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

6 filings

States

6

Affected · reported

61

First → last filing

Dec 23, 2025

Merge confidence

100%

incident inc_9b352cd1863b445d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings. The filings describe a phishing attack. Intrusion Oct 9, 2025–Oct 26, 2025, discovered Nov 7, 2025 — the first regulatory filing landed 46 days later. 61 individuals reported across the linked filings. Data reported: Government ID, Financial account, Identity (basic), and 1 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
46days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Filing span
0days

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 clocksVermont⏱ VT AG >14 bdayMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 9, 2025breach begins
Nov 7, 2025discovered
notification delay · 46 days
Dec 23, 2025first filing
—watching for filings

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

Member cascade — every filing about this breach

  1. DEC 23MA AGMA AG noticefirst filing · 31 MA residentsday 0
  2. DEC 23MT AGMT AG notice15 MT residentsday 0
  3. DEC 23NH AGNH AG notice2 NH residentsday 0
  4. DEC 23VT AGVT AG noticeno count statedday 0
  5. DEC 23NE AGNE AG notice4 NE residentsday 0
  6. DEC 23IN AGIN AG noticemost recent · 9 IN residentsday 0
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 9, 2025 – Oct 26, 2025
MT AG
Discovered
Nov 7, 2025· 29d undetected
MT AG + NH AG + VT AG +1
Data types
Financial account · Identity (basic) · Government ID · PII
MA AG + MT AG + NH AG +2
Attack vector
Phishing
MT AG

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

Affected residents by state

per-state reported counts

MA31
MT15
IN9
NE4
NH2

State AGs report only their own residents; teal bars show each state's reported slice.

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 filing6 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

0 days

Cadence

~1 / 0d

vs. multi-state median

20.0× faster

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.