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

ADVANCE STORES COMPANY, INCORPORATED — April 2024 breach

Clustered 12 filings across 12 jurisdictions · filing window Jul 10, 2024 → Jul 11, 2024 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

12

Affected · reported

2,316,591

First → last dated filing

Jul 10, 2024 → Jul 11, 2024

Merge confidence

100%

incident inc_7b4e3807969a4b4f · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. The filings describe hacking. Intrusion Apr 14, 2024–May 24, 2024, discovered Apr 14, 2024. 2,316,591 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
57days

Range of discovered_at dates across filings

Filing span
1days

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 bdayMaine⏱ ME AG >30d · 48dWashington⏱ WA AG >30dCalifornia✓ CA 60-day OK · 48dOregon✓ OR AG ≤45dMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 14, 2024breach begins
Apr 14, 2024discovered · members disagree
Jul 10, 2024first dated filing
Jul 11, 2024most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. JUL 1IL AGIL AG noticefiling day not on record · no count stated—
  2. JUL 10VT AGVT AG noticefirst filing · no count statedday 0
  3. JUL 10MT AGMT AG notice9,084 MT residentsday 0
  4. JUL 10DE AGDE AG notice6,693 DE residentsday 0
  5. JUL 10NH AGNH AG notice5,741 NH residentsday 0
  6. JUL 10CA AGCA AG noticeno count statedday 0
  7. JUL 10OR AGOR AG noticestates nationwide total 2,316,591day 0
  8. JUL 10ME AGME AG noticestates nationwide total 2,316,591day 0
  9. JUL 10MA AGMA AG notice29,102 MA residentsday 0
  10. JUL 10WA AGWA AG notice21,791 WA residentsday 0
  11. JUL 10IN AGIN AG noticestates nationwide total 2,316,590day 0
  12. JUL 11SC AGSC AG noticemost recent · 64,107 SC residents+1d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 14, 2024 – May 24, 2024
VT AG
Discovered
Apr 14, 2024IL AGMay 23, 2024VT AG + MT AG + DE AG +5Jun 10, 2024OR AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
VT AG + MT AG + DE AG +6
Attack vector
Third-Party / Supply Chain
VT 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)

2,316,591

Sum of filed state slices

218,354· 9.4% of stated

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

US2,316,591
IN67,978
SC64,107
MA29,102
WA21,791
ME13,858
MT9,084
DE6,693
NH5,741

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 filing12 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 22, 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

1 days

Cadence

~1 / 0.1d

vs. multi-state median

6.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.