GLOBALClaimed by AbyssFirst sightinglinked via operator-confirmed · 100%
Posted to leak site Jun 30, 2024bd_5f666f0a00d5b193
crimsonwinegroup.com.com 1.6Tb uncompressed data
Clustered 8 filings across 6 jurisdictions · filing window Jun 30, 2024 → Dec 13, 2024. View entity profile → Other incidents for this victim →
incident inc_d5d8558939954da5 · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Discovery to SEC materiality determination
Materiality determination to SEC 8-K filing
Time between earliest and latest filing
PII
FEDERAL ME MT OR WA
Leak Site · SEC 8-K · State AG
per-filing reported counts
State AGs report only their own residents; bars show per-filing counts.
Earliest sighting first · deep chronology in Litigation Timeline
8 filings across 6 jurisdictions · Jun 30, 2024 – Dec 13, 2024 · 4 milestones
Jun 30, 2024
When the intrusion reportedly occurred, per the linked filings
Jun 30, 2024
Reported by SEC 8-K, WASHINGTON AG filings
crimsonwinegroup.com.com 1.6Tb uncompressed data
Jul 5, 2024
Registrant determined the incident material — starts the SEC 4-business-day clock
Crimson Wine Group, Ltd. filed an 8-K on July 5, 2024, reporting a cybersecurity incident discovered on June 30, 2024. An unauthorized third party gained access to certain technology systems. The Company is in the early stages of its investigation, and the scope of costs and impacts has not been determined. The incident status is active.
Jul 15, 2024
Reported by MAINE AG filing
Crimson Wine Group disclosed on July 25, 2024 that a June 30, 2024 cybersecurity incident involving unauthorized third-party access to internal systems and exfiltration of files (potentially including sensitive personal information) has likely had a material impact on business operations. The company shut down systems to contain the incident, engaged external cybersecurity experts, and has substantially restored affected systems. Scope of personal information exposure is still under investigation.
crimsonwinegroup.com.com 1.6Tb uncompressed data
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.
Crimson Wine Group, a business sector entity reported a ransomware incident to the Washington Attorney General. The organization became aware of the incident on 2024-06-30 and filed notice on 2024-12-13. 3,436 Washington residents were affected. 166 days elapsed between awareness and notification. 4 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 3,436
Crimson Wine Group reported a data breach to the Montana Attorney General. The breach was reported on 2024-12-13. The breach occurred from 06/26/2024 to 06/30/2024. 17 Montana residents were affected.
Affected (this filing): 17
Crimson Wine Group experienced an external system breach (hacking) between June 26, 2024, and June 30, 2024. The breach was discovered on July 15, 2024. The incident affected 26,238 individuals in total, including 21 residents of Maine. Affected individuals were notified on August 19, 2024, and offered 12 months of identity monitoring services from IDX.
Affected (this filing): 21
Crimson Wine Group reported a data breach to the Oregon Attorney General. The breach was reported on 2024-12-13. 26,238 individuals were affected.
Affected (this filing): 26,238