DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteState AGConfirmed7 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlockbit_3high sensitivity
Merged incident · 7 filings

Nautic Partners — February 2023 breach

Clustered 7 filings across 6 jurisdictions · filing window Jul 11, 2022 → Jan 16, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 filings

States

5

Affected · reported

7,870

First → last filing

Jul 11, 2022 → Jan 16, 2024

Merge confidence

100%

incident inc_65b936a201da486d · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Feb 23, 2023–Apr 5, 2023, discovered Dec 29, 2023. 7,870 individuals reported across the linked filings. Data reported: Government ID, Financial account, PCI, and 3 more. Notifications rolled out on a 554-day schedule across 6 filings beginning Jul 11, 2022. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Leak precedence
Noneclaim trailed by 268d

Days between the first leak-site claim and the first regulatory filing. 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.

Filing span
554days

Time between earliest and latest filing

Not recorded for this incident

Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.

Regulatory clocksLeak gap✗ Leak >180dMassachusetts✓ MA credit monitoring dueMaine✓ ME AG ≤30d · 14dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 23, 2023breach begins
Dec 29, 2023discovered
Jul 11, 2022first filing
Jan 16, 2024most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. JUL 11MA AGMA AG noticefirst filing · 7 MA residentsday 0
  2. APR 5Leak sitelockbit_3 postattacker claim · unverified+268d
  3. JAN 12ME AGME AG noticestates nationwide total 7,870+550d
  4. JAN 12IN AGIN AG noticestates nationwide total 7,870+550d
  5. JAN 12MA AGMA AG notice526 MA residents+550d
  6. JAN 12CA AGCA AG noticeno count stated+550d
  7. JAN 16NH AGNH AG noticemost recent · 19 NH residents+554d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 23, 2023 – Apr 5, 2023
ME AG
Discovered
Dec 29, 2023· 309d undetected
ME AG
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PII
MA AG + ME AG + CA AG +1
Attack vector
Unauthorized Access
ME 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)

7,870

Sum of filed state slices

611· 7.8% of stated

92% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US7,870
MA526
IN62
NH19
ME4

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

Leak-site claim1 member

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing6 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
human
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

554 days

Cadence

~1 / 92.3d

vs. multi-state median

69.3× 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.