DisclosureLens
Leak SiteHHS OCRState AGConfirmed13 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedmarketohigh sensitivity
Merged incident · 13 filings

Sea Mar Community Health Centers — December 2020 breach

Clustered 13 filings across 10 jurisdictions · filing window Oct 29, 2021 Apr 1, 2022. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

13 filings

States

9

Affected · reported

688,000

First → last filing

Oct 29, 2021 Apr 1, 2022

Merge confidence

100%

incident inc_b34395ee23524a6d · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Dec 1, 2020–Mar 31, 2021, discovered Jun 24, 2021 — the first regulatory filing landed 127 days later (flagged late). 688,000 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 2 more. Notifications rolled out on a 154-day schedule across 12 filings beginning Oct 29, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
127days

Discovered → first regulatory filing

Discovery variance
208days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 39d

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

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delayno SEC 8-K in this cluster.

Regulatory clocksOregon OR AG >45dCalifornia CA 60-day late · 69dWashington WA AG >90dMaine ME AG >30d · 67dLeak gap Leak >90dHIPAA HHS notifiedMassachusetts MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 1, 2020breach begins
Jun 24, 2021discovered · members disagree
notification delay · 127 days
Oct 29, 2021first filing
Apr 1, 2022most 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. OCT 29MT AGMT AG noticefirst filing · 808 MT residentsday 0
  2. OCT 29IN AGIN AG noticestates nationwide total 651,500day 0
  3. OCT 30HHS OCRHHS OCR noticestates nationwide total 688,000+1d
  4. NOV 1OR AGOR AG noticestates nationwide total 651,500+3d
  5. NOV 1NH AGNH AG noticestates nationwide total 39+3d
  6. NOV 5MA AGMA AG notice99 MA residents+7d
  7. NOV 5ME AGME AG noticestates nationwide total 651,500+7d
  8. NOV 5CA AGCA AG noticeno count stated+7d
  9. NOV 15WA AGWA AG notice628,569 WA residents+17d
  10. DEC 7Leak sitemarketo postattacker claim · unverified+39d
  11. JAN 1IL AGIL AG noticeno count stated+64d
  12. APR 1NH AGNH AG notice13 NH residents+154d
  13. APR 1CA AGCA AG noticemost recent · no count stated+154d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 1, 2020Mar 31, 2021
MT AG
Discovered
Jun 24, 2021MT AG + NH AG + CA AG +1Aug 30, 2021OR AG + ME AGOct 29, 2021IL AGJan 18, 2022NH AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI · PII
MT AG + HHS OCR + NH AG +4
Attack vector
Unauthorized Access
MT 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)

688,000

Sum of filed state slices

629,761· 91.5% of stated

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

US688,000
WA628,569
MT808
IN214
MA99
ME58
NH13

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 filing12 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 25, 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

154 days

Cadence

~1 / 12.8d

vs. multi-state median

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