LKQ CORPORATION
bd_6b3dcc0a0ce73b64 · schema v1 · pii pii-v1
Full breach record for LKQ CORPORATION →3 incidents on fileLKQ Corporation reported a data breach to the Massachusetts Office of Consumer Affairs and Business Regulation. The breach was reported on 2025-12-16. 189 Massachusetts residents were affected.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Dec 16, 2025
Filed
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Sitecl0pbd_ca963b548e29a5612025-10-27 · +50dVerified by operator
Regulatory filings (9) · sorted by filing gap
- Texas State AGbd_9f980168ee3c217d2025-12-16Verified
- Indiana State AGbd_0d24498ef978ea452025-12-15 · +1dVerified
- Maine State AGbd_222597b2166e9a952025-12-15 · +1dVerified
- Montana State AGbd_3b11067f5766d01d2025-12-15 · +1dVerified
Show 5 more filings ↓Show fewer ↑up to 15d gap
- New Hampshire State AGbd_6c3aa51f5e66e7ed2025-12-15 · +1dVerified
- Nebraska State AGbd_a883eb69b4b810b72025-12-15 · +1dVerified
- Vermont State AGbd_e09da3b67b0dfe832025-12-15 · +1dVerified
- California State AGbd_f78e0c2f9e23cbd92025-12-15 · +1dVerified
- Illinois State AGbd_290f5cb85d1397ca2025-12-01 · +15dCandidate
Filing propagation · 10 filings · 10 states
View merged incident ↗Pattern: first filing Dec 1 (IL), last Dec 16 (MA) — a 15-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.