Clustered 3 filings across 2 jurisdictions · filing window Jan 7, 2025 → May 12, 2025. View entity profile → Other incidents for this victim →
incident inc_dbc0971e90694deb · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Materiality delta · SEC filing delay — no SEC 8-K in this cluster.
VT
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 15, 2024
When the intrusion reportedly occurred, per the linked filings
Jan 7, 2025
Reported by VERMONT AG filings
Sunflower Medical Group With only 7 days to spare, take the opportunity to bet on exclusive, unique, and impressive data. More than 400 thousand driver's licenses, insurance cards, social security numbers. Sql base is more than 3TB. Open your wallets and get ready to buy exclusive data. We sell only to one person, no resale, you will be the only owner!
Sunflower Medical Group, P.A. notified consumers of a data breach where an unknown third party accessed systems on or about Dec 15, 2024. Personal information was acquired. The company engaged forensic investigators, enhanced security measures, and offered one year of Experian IdentityWorks credit monitoring. No evidence of fraud was found.
Sunflower Medical Group, P.A. notified consumers of a data breach where an unauthorized third party accessed systems on or about December 15, 2024. Personal information was acquired. The company engaged forensic investigators, secured systems, and offered one year of Experian IdentityWorks credit monitoring. No evidence of fraud was found.
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.