Southern Tide LLC — April 2017 breach
Clustered 3 filings across 3 jurisdictions · filing window Jun 15, 2017 → Jun 20, 2017. View entity profile → Other incidents for this victim →
incident inc_62ab512e31b5411c · merged by deterministic · confidence 100%
Litigation Timing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Sensitive data
authenticationfinancial_credentialsIncident timeline
No discovery date is recorded on any filing in this cluster, so the notification delay is not computable. Dashed segments fill in as filings merge.
Member cascade — every filing about this breach
- JUN 15MT AGMT AG noticefirst filing · 3 MT residentsday 0
- JUN 15NH AGNH AG notice17 NH residentsauto-linkedday 0
- JUN 20MA AGMA AG noticemost recent · 165 MA residentsauto-linked+5d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Apr 27, 2017 – Jun 7, 2017 MT AG
- Discovered
- —
- Data types
- Authentication · Financial account · Financial credentials · Identity (basic) · PCI MT AG + NH AG + MA AG
- Attack vector
- Unauthorized Access MT AG
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Affected residents by state
per-state reported counts
State AGs report only their own residents; teal bars show each state's reported slice.
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
- 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
5 days
Cadence
~1 / 2.5d
vs. multi-state median
1.6× faster
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.