DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed7 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedcactushigh sensitivity
Merged incident · 7 filings

Asbury Automotive Group, Inc. — December 2023 breach

Clustered 7 filings across 7 jurisdictions · filing window Jan 12, 2024 → Apr 24, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 filings

States

6

Affected · reported

41,571

First → last filing

Jan 12, 2024 → Apr 24, 2024

Merge confidence

100%

incident inc_45706237801c4a21 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Dec 25, 2023, discovered Dec 25, 2023 — the first regulatory filing landed 121 days later (flagged late). 41,571 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 102-day schedule across 6 filings beginning Jan 12, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
121days

Discovered → first regulatory filing

Discovery variance
91days

Range of discovered_at dates across filings

Leak precedence
102days 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
102days

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 bdayLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 25, 2023breach begins
Dec 25, 2023discovered · members disagree
notification delay · 121 days
Apr 24, 2024first filing
—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. JAN 12Leak sitecactus postfirst filing · attacker claim · unverifiedday 0
  2. APR 24MT AGMT AG notice7 MT residents+102d
  3. APR 24NH AGNH AG notice6 NH residents+102d
  4. APR 24ME AGME AG notice2 affected+102d
  5. APR 24IN AGIN AG noticestates nationwide total 41,571+102d
  6. APR 24MA AGMA AG notice21 MA residents+102d
  7. APR 24VT AGVT AG noticemost recent · no count stated+102d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 25, 2023
MT AG
Discovered
Dec 25, 2023MT AG + NH AG + VT AGMar 25, 2024ME AGfilings disagree on discovery
Data types
Identity (basic) · Government ID · PII
MT AG + NH AG + ME AG +2
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)

41,571

Sum of filed state slices

2,009· 4.8% of stated

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

US41,571
IN1,973
MA21
MT7
NH6
ME2

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 filing6 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 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

102 days

Cadence

~1 / 17d

vs. multi-state median

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