Sovos Compliance, LLC — May 2023 breach
Clustered 22 filings across 9 jurisdictions · filing window Jul 12, 2023 → Sep 22, 2023. View entity profile → Other incidents for this victim →
incident inc_530aa2a84d724341 · merged by deterministic · confidence 100%
Litigation Timing
SupplementalDiscovered → first regulatory filing
Range of discovered_at dates across filings
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
Sensitive data
identity_governmentIncident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- JUL 12DE AGDE AG noticefirst filing · no count statedauto-linkedday 0
- JUL 12NH AGNH AG noticeno count statedauto-linkedday 0
- JUL 12VT AGVT AG noticeno count statedauto-linkedday 0
- JUL 12MT AGMT AG notice237 MT residentsday 0
- JUL 13ME AGME AG noticestates nationwide total 18,513auto-linked+1d
- JUL 13CA AGCA AG noticeno count statedoperator-confirmed+1d
- AUG 7MT AGMT AG notice189 MT residentsoperator-confirmed+26d
- AUG 8HHS OCRHHS OCR noticestates nationwide total 18,261auto-linked+27d
- AUG 23VT AGVT AG noticeno count statedauto-linked+42d
- AUG 23DE AGDE AG noticeno count statedoperator-confirmed+42d
- AUG 23NH AGNH AG noticeno count statedauto-linked+42d
- AUG 23OR AGOR AG noticestates nationwide total 215,114operator-confirmed+42d
- AUG 23ME AGME AG noticestates nationwide total 215,114operator-confirmed+42d
- AUG 23WA AGWA AG noticeno count statedoperator-confirmed+42d
- AUG 23CA AGCA AG noticeno count statedauto-linked+42d
- SEP 5ME AGME AG noticestates nationwide total 215,114operator-confirmed+55d
- SEP 22CA AGCA AG noticeno count statedoperator-confirmed+72d
- SEP 22OR AGOR AG noticestates nationwide total 181,507operator-confirmed+72d
- SEP 22NH AGNH AG notice59 NH residentsauto-linked+72d
- SEP 22ME AGME AG noticestates nationwide total 181,507operator-confirmed+72d
- SEP 22VT AGVT AG noticeno count statedauto-linked+72d
- SEP 22WA AGWA AG noticemost recent · 1,450 WA residentsoperator-confirmed+72d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- May 30, 2023 NH AG
- Discovered
- May 31, 2023DE AG + NH AG + MT AG +3Jun 12, 2023ME AG + WA AGJul 20, 2023OR AGfilings disagree on discovery
- Data types
- Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII DE AG + NH AG + VT AG +5
- Attack vector
- Unauthorized Access DE 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)
215,114
Sum of filed state slices
1,812· 0.8% of stated
99% 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
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
Merge provenance
- Method
- deterministic
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- Reviewed
- operator-reviewed Jun 12, 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
72 days
Cadence
~1 / 3.4d
vs. multi-state median
9.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.