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

LKQ CORPORATION — August 2025 breach

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

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

11 filings

States

10

Affected · reported

9,070

First → last filing

Oct 27, 2025 → Dec 16, 2025

Merge confidence

100%

incident inc_dae52e1de1034c5d · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Aug 1, 2025–Oct 2, 2025, discovered Oct 1, 2025 — the first regulatory filing landed 61 days later (flagged late). 9,070 individuals reported across the linked filings. Data reported: Government ID, PII, and Identity (basic). Notifications rolled out on a 49-day schedule across 10 filings beginning Oct 27, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
61days

Discovered → first regulatory filing

Discovery variance
2days

Range of discovered_at dates across filings

Leak precedence
34days before filing

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
49days

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 bdayTexas✗ TX AG >30dLeak gap⏱ Leak >30dMaine⏱ ME AG >30d · 73dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Aug 1, 2025breach begins
Oct 1, 2025discovered · members disagree
notification delay · 61 days
Dec 1, 2025first filing
Dec 16, 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. OCT 27Leak sitecl0p postfirst filing · attacker claim · unverifiedday 0
  2. DEC 1IL AGIL AG noticeno count stated+35d
  3. DEC 15MT AGMT AG notice25 MT residents+49d
  4. DEC 15NH AGNH AG notice27 NH residents+49d
  5. DEC 15CA AGCA AG noticeno count stated+49d
  6. DEC 15ME AGME AG noticestates nationwide total 9,070+49d
  7. DEC 15VT AGVT AG noticeno count stated+49d
  8. DEC 15IN AGIN AG noticestates nationwide total 9,070+49d
  9. DEC 15NE AGNE AG noticeno count stated+49d
  10. DEC 16TX AGTX AG noticestates nationwide total 9,070+50d
  11. DEC 16MA AGMA AG noticemost recent · 189 MA residents+50d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Aug 1, 2025
NH AG
Discovered
Oct 1, 2025MT AGOct 3, 2025IL AG + NH AG + CA AG +4filings disagree on discovery
Data types
Identity (basic) · Government ID · PII
IL AG + MT AG + NH AG +6
Attack vector
Unauthorized Access
MT 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)

9,070

Sum of filed state slices

1,580· 17.4% of stated

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

US9,070
TX1,119
IN189
MA189
ME31
NH27
MT25

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 claim1 member

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

Press / market report

No press coverage linked yet.

State AG / regulator filing10 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 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

49 days

Cadence

~1 / 4.9d

vs. multi-state median

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