DisclosureLens
Leak SiteSEC 8-KState AGConfirmed12 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedabysshigh sensitivity
Merged incident · 12 filings

Crimson Wine Group, Ltd. — June 2024 breach

Clustered 12 filings across 10 jurisdictions · filing window Jun 30, 2024 Dec 14, 2024. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

12 filings

States

9

Affected · reported

26,238

First → last filing

Jun 30, 2024 Dec 14, 2024

Merge confidence

100%

incident inc_0fe2732d2819427c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings and 2 unverified claims. Intrusion Jun 26, 2024–Jun 30, 2024, discovered Jun 26, 2024 — the first regulatory filing landed 9 days later (flagged late). 26,238 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 4 more. Notifications rolled out on a 167-day schedule across 10 filings beginning Jun 30, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
9days

Discovered → first regulatory filing

Discovery variance
4days

Range of discovered_at dates across filings

Leak precedence
5days 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.

Materiality delta
25days

Discovery to SEC materiality determination

SEC filing delay
0days

Materiality determination to SEC 8-K filing

Filing span
167days

Time between earliest and latest filing

Regulatory clocksMaine ME AG >90d · 166dVermont VT AG >45 bdayWashington WA AG >90dLeak gap Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 26, 2024breach begins
Jun 26, 2024discovered · members disagree
notification delay · 9 days
Jul 5, 2024first filing
Dec 14, 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 30Leak siteabyss postfirst filing · attacker claim · unverifiedday 0
  2. JUL 5SEC 8-KSEC 8-K noticeno count stated+5d
  3. JUL 25SEC 8-KSEC 8-K noticeno count stated+25d
  4. JUL 25Leak siteabyss postattacker claim · unverified+25d
  5. DEC 1IL AGIL AG noticeno count stated+154d
  6. DEC 13MT AGMT AG notice17 MT residents+166d
  7. DEC 13ME AGME AG noticestates nationwide total 26,238+166d
  8. DEC 13VT AGVT AG noticeno count stated+166d
  9. DEC 13OR AGOR AG noticestates nationwide total 26,238+166d
  10. DEC 13WA AGWA AG notice3,436 WA residents+166d
  11. DEC 13NH AGNH AG notice59 NH residents+166d
  12. DEC 14MA AGMA AG noticemost recent · 212 MA residents+167d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 30, 2024
SEC 8-K
Discovered
Jun 26, 2024IL AGJun 30, 2024SEC 8-K + MT AG + ME AG +3filings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII
SEC 8-K + MT AG + ME AG +4
Attack vector
Unauthorized Access
SEC 8-K

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)

26,238

Sum of filed state slices

3,745· 14.3% of stated

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

US26,238
WA3,436
MA212
NH59
ME21
MT17

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

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement2 members

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 23, 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

167 days

Cadence

~1 / 15.2d

vs. multi-state median

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