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

Jeff Wyler Automotive Family Inc. — May 2023 breach

Clustered 8 filings across 7 jurisdictions · filing window Jun 13, 2023 → Mar 4, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

8 filings

States

6

Affected · reported

76,038

First → last filing

Jun 13, 2023 → Mar 4, 2024

Merge confidence

100%

incident inc_96a4a6c282ce473b · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion May 27, 2023, discovered Jan 29, 2024 — the first regulatory filing landed 15 days later (flagged late). 76,038 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Financial account, and 4 more. Notifications rolled out on a 265-day schedule across 6 filings beginning Jun 13, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
15days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
245days 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
265days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap✗ Leak >180dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 27, 2023breach begins
Jan 29, 2024discovered
notification delay · 15 days
Feb 13, 2024first filing
Mar 4, 2024most 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. JUN 13Leak site8base postfirst filing · attacker claim · unverifiedday 0
  2. JUL 4Leak sitecryptbb postattacker claim · unverified+21d
  3. FEB 13VT AGVT AG noticeno count stated+245d
  4. FEB 13IN AGIN AG noticestates nationwide total 76,038+245d
  5. FEB 15ME AGME AG notice12 affected+247d
  6. FEB 19MT AGMT AG notice4 MT residents+251d
  7. FEB 23NH AGNH AG notice12 NH residents+255d
  8. MAR 4MA AGMA AG noticemost recent · 58 MA residents+265d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 27, 2023
IN AG
Discovered
Jan 29, 2024· 247d undetected
ME AG + NH AG
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
VT AG + ME AG + MT AG +2
Attack vector
Unauthorized Access
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)

76,038

Sum of filed state slices

5,156· 6.8% of stated

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

US76,038
IN5,070
MA58
ME12
NH12
MT4

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

265 days

Cadence

~1 / 37.9d

vs. multi-state median

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