DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed7 records · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedgenesishigh sensitivity
Merged incident · 7 records

The American Board of Preventive Medicine — March 2026 breach

Clustered 7 records across 6 jurisdictions: 6 filings and 1 leak-site claim · filing window Oct 12, 2026 → Oct 19, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 records

States

6

Affected · reported

23,692

First → last dated filing

Oct 12, 2026 → Oct 19, 2026

Merge confidence

100%

incident inc_d43906d6a3274616 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 6 regulatory filings and 1 unverified claim. The filing describes unauthorized access. Intrusion Mar 8, 2026–Mar 10, 2026, discovered Sep 24, 2026. 23,692 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PHI, and 3 more. Notifications rolled out on a 7-day schedule across 5 dated filings beginning Oct 12, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Filing span
7days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 8, 2026breach begins
Sep 24, 2026discovered
Oct 12, 2026first dated filing
Oct 19, 2026most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing and leak-site claim in this incident

  1. MAY 8Leak sitegenesis postfirst record · attacker claim · unverifiedday 0
  2. OCT 1MA AGMA AG noticefiling day not on record · 358 MA residents—
  3. OCT 12DE AGDE AG noticeno count stated+157d
  4. OCT 13CA AGCA AG noticeno count stated+158d
  5. OCT 14VT AGVT AG notice352 VT residents+159d
  6. OCT 16TX AGTX AG noticestates nationwide total 23,692+161d
  7. OCT 19NH AGNH AG noticemost recent · 81 NH residents+164d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 8, 2026 – Mar 10, 2026
DE AG
Discovered
Sep 24, 2026· 200d undetected
DE AG
Data types
Credentials · Financial account · Health (basic) · Identity (basic) · Government ID · PHI
MA AG + DE AG + CA AG +3
Attack vector
Unauthorized Access
NH 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)

23,692

Sum of filed state slices

1,746· 7.4% of stated

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

US23,692
TX955
MA358
VT352
NH81

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
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 21, 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

7 days

Cadence

~1 / 1.8d

vs. multi-state median

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