DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed10 filings · 8 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcl0phigh sensitivity
Merged incident · 10 filings

AutoZone, Inc. — May 2023 breach

Clustered 10 filings across 9 jurisdictions · filing window Jan 1, 2023 → Apr 19, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

8

Affected · reported

184,995

First → last filing

Jan 1, 2023 → Apr 19, 2024

Merge confidence

100%

incident inc_3678c622a2db41f0 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 2 unverified claims. The filings describe hacking. Intrusion May 28, 2023, discovered May 30, 2023. 184,995 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 1 more. Notifications rolled out on a 474-day schedule across 8 filings beginning Jan 1, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
157days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 187d

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
474days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksVermont✗ VT AG >45 bdayWashington✗ WA AG >90dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 28, 2023breach begins
May 30, 2023discovered · members disagree
Jan 1, 2023first filing
Nov 22, 2023most 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. JAN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JUL 7Leak sitecl0p postattacker claim · unverified+187d
  3. NOV 20CA AGCA AG noticeno count stated+323d
  4. NOV 20MT AGMT AG notice299 MT residents+323d
  5. NOV 20ME AGME AG noticestates nationwide total 184,995+323d
  6. NOV 21OR AGOR AG noticestates nationwide total 184,995+324d
  7. NOV 21VT AGVT AG noticeno count stated+324d
  8. NOV 21MA AGMA AG notice2,019 MA residents+324d
  9. NOV 22WA AGWA AG notice2,509 WA residents+325d
  10. APR 19Leak sitedispossessor postmost recent · attacker claim · unverified+474d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 28, 2023
CA AG
Discovered
May 30, 2023IL AGJun 5, 2023WA AGAug 15, 2023MT AG + VT AGNov 3, 2023ME AG + OR AGfilings disagree on discovery
Data types
Financial account · Identity (basic) · Government ID · PII
CA AG + MT AG + VT AG +3
Attack vector
Third-Party / Supply Chain
CA 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)

184,995

Sum of filed state slices

5,120· 2.8% of stated

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

US184,995
WA2,509
MA2,019
MT299
ME293

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 claim2 members

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing8 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
Reviewed
operator-reviewed Aug 23, 2026 · at least one link edge was human-adjudicated
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

474 days

Cadence

~1 / 52.7d

vs. multi-state median

52.7× 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.