DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteHHS OCRState AGConfirmed10 filings · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedkarakurthigh sensitivity
Merged incident · 10 filings

Our Sunday Visitor — March 2023 breach

Clustered 10 filings across 7 jurisdictions · filing window Apr 29, 2023 → Sep 22, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

6

Affected · reported

2,743

First → last filing

Apr 29, 2023 → Sep 22, 2023

Merge confidence

100%

incident inc_012b18c5eed8433e · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Mar 3, 2023–Mar 8, 2023, discovered Mar 8, 2023 — the first regulatory filing landed 58 days later (flagged late). 2,743 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 3 more. Notifications rolled out on a 146-day schedule across 9 filings beginning Apr 29, 2023. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
58days

Discovered → first regulatory filing

Discovery variance
57days

Range of discovered_at dates across filings

Leak precedence
6days before filing

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
146days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksVermont✗ VT AG >45 bdayLeak gap⏱ Leak >90dHIPAA✓ HHS notifiedMassachusetts✓ MA credit monitoring dueMaine✓ ME AG ≤30d · 12dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 3, 2023breach begins
Mar 8, 2023discovered · members disagree
notification delay · 58 days
May 5, 2023first filing
Sep 22, 2023most 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. APR 29Leak sitekarakurt postfirst filing · attacker claim · unverifiedday 0
  2. MAY 5HHS OCRHHS OCR noticestates nationwide total 1,508+6d
  3. MAY 16IN AGIN AG noticestates nationwide total 2,743+17d
  4. MAY 16MT AGMT AG notice1 MT residents+17d
  5. MAY 16MA AGMA AG notice42 MA residents+17d
  6. MAY 16ME AGME AG noticestates nationwide total 2,743+17d
  7. MAY 16VT AGVT AG noticeno count stated+17d
  8. MAY 23NH AGNH AG notice13 NH residents+24d
  9. SEP 22VT AGVT AG noticeno count stated+146d
  10. SEP 22NH AGNH AG noticemost recent · 16 NH residents+146d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 8, 2023
IN AG
Discovered
Mar 8, 2023MT AG + VT AG + NH AGMay 4, 2023ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + MT AG + NH AG +3
Attack vector
Unauthorized Access
HHS OCR

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)

2,743

Sum of filed state slices

2,570· 93.7% of stated

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

US2,743
IN2,509
MA42
NH16
ME2
MT1

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 filing9 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
deterministic
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

146 days

Cadence

~1 / 16.2d

vs. multi-state median

18.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.