DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed5 records · 3 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedspacebearshigh sensitivity
Merged incident · 5 records

Pineland community service board — November 2024 breach

Clustered 5 records across 3 jurisdictions: 3 filings and 2 leak-site claims · filing window Mar 20, 2025 → Aug 27, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 records

States

3

Affected · reported

19,010

First → last filing

Mar 20, 2025 → Aug 27, 2025

Merge confidence

100%

incident inc_3c336cc5f8bd4082 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 3 regulatory filings and 2 unverified claims. The filing describes unauthorized access. Intrusion Nov 24, 2024. 19,010 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 1 more. Notifications rolled out on a 160-day schedule across 3 filings beginning Mar 20, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Leak precedence
56days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
160days

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 >180dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 24, 2024breach begins
Mar 20, 2025first filing
Aug 27, 2025most recent filing

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 and leak-site claim in this incident

  1. JAN 23Leak sitespacebears postfirst record · attacker claim · unverifiedday 0
  2. FEB 3Leak sitespacebears postattacker claim · unverified+11d
  3. MAR 20HHS OCRHHS OCR noticestates nationwide total 19,010+56d
  4. AUG 26IN AGIN AG noticestates nationwide total 4,001+215d
  5. AUG 27MA AGMA AG noticemost recent · 2 MA residents+216d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Nov 24, 2024
IN AG
Discovered
—
Data types
Health (basic) · Identity (basic) · Government ID · PHI
HHS OCR + MA AG
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)

19,010

Sum of filed state slices

4· 0.0% of stated

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

Evidence ladder — rungs this incident occupies

Leak-site claim2 members

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

Press / market report

No press coverage linked yet.

State AG / regulator filing3 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 22, 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

160 days

Cadence

~1 / 80d

vs. multi-state median

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