Confirmed breach. Intrusion Jul 17, 2023, discovered Aug 5, 2023 — the first regulatory filing landed 293 days later (flagged late). 2,025 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksWashington✗ WA AG >90dFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforced
Affected (total reported)
2,025
Data types
—
Jurisdictions
2
IN WA
Linked filings
2
all State AG
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jul 17, 2023
When the intrusion reportedly occurred, per the linked filings
Breach discoveredAG web form
Aug 5, 2023
Reported by WASHINGTON AG filing
293 days
🏎️Indiana State AGFirst filinglinked via multistate filing link · 100%
Messner Reeves LLP on behalf of Chipotle Mexican Grill Inc reported a data breach to the Indiana Attorney General. The breach occurred on 2023-07-17 and was reported on 2024-05-24. 2 Indiana residents were affected. 2,025 individuals affected in total.
Messner Reeves on behalf of Chipotle Mexican Grill, Inc., a business sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2023-08-05 and filed notice on 2024-05-24. 678 Washington residents were affected. 293 days elapsed between awareness and notification. 19 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 678
WA AG >90d
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.