Crimson Wine Group, Ltd. — June 2024 breach
Clustered 11 records across 9 jurisdictions: 10 filings and 1 leak-site claim · filing window Jul 5, 2024 → Dec 14, 2024 (dated filings only). View entity profile → Other incidents for this victim →
incident inc_0fe2732d2819427c · merged by deterministic · confidence 100%
Litigation Timing
SupplementalDiscovered → first regulatory filing
Range of discovered_at dates across filings
Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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.
Discovery to SEC materiality determination
Materiality determination to SEC 8-K filing
Time between earliest and latest filing
Sensitive data
identity_governmentIncident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.
Member cascade — every filing and leak-site claim in this incident
- JUN 30Leak siteabyss postfirst record · attacker claim · unverifiedoperator-confirmedday 0
- JUL 5SEC 8-KSEC 8-K noticeno count statedoperator-confirmed+5d
- JUL 25SEC 8-KSEC 8-K noticeno count statedoperator-confirmed+25d
- DEC 1IL AGIL AG noticefiling day not on record · no count stated—
- DEC 13VT AGVT AG noticeno count statedauto-linked+166d
- DEC 13OR AGOR AG noticestates nationwide total 26,238auto-linked+166d
- DEC 13ME AGME AG noticestates nationwide total 26,238auto-linked+166d
- DEC 13NH AGNH AG notice59 NH residentsauto-linked+166d
- DEC 13MT AGMT AG notice17 MT residentsauto-linked+166d
- DEC 13WA AGWA AG notice3,436 WA residentsauto-linked+166d
- DEC 14MA AGMA AG noticemost recent · 212 MA residentsauto-linked+167d
- 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 + VT AG + ME AG +3filings disagree on discovery
- Data types
- Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI · PII SEC 8-K + VT 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.
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
Attacker assertion only. Establishes: claim date, group, alleged victim.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
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
162 days
Cadence
~1 / 20.3d
vs. multi-state median
27.0× 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.