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

BELL AMBULANCE, INC. — February 2025 breach

Clustered 8 filings across 6 jurisdictions · filing window Jan 15, 2025 → Mar 9, 2026. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

8 filings

States

5

Affected · reported

237,830

First → last filing

Jan 15, 2025 → Mar 9, 2026

Merge confidence

100%

incident inc_0cc8da39671c4e8f · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Feb 7, 2025–Feb 14, 2025, discovered Feb 13, 2025. 237,830 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PHI, and 1 more. Notifications rolled out on a 418-day schedule across 7 filings beginning Jan 15, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 47d

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

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksLeak gap✗ Leak >180dVermont✗ VT AG >45 bdayMaine✗ ME AG >90d · 389dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Feb 7, 2025breach begins
Feb 13, 2025discovered
Jan 15, 2025first filing
Mar 9, 2026most 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. JAN 15NE AGNE AG noticefirst filing · no count statedday 0
  2. MAR 2Leak sitemedusa postattacker claim · unverified+47d
  3. APR 14HHS OCRHHS OCR noticestates nationwide total 237,830+89d
  4. JAN 15MA AGMA AG notice12 MA residents+365d
  5. JAN 15VT AGVT AG noticeno count stated+365d
  6. MAR 9ME AGME AG noticestates nationwide total 237,830+418d
  7. MAR 9VT AGVT AG noticeno count stated+418d
  8. MAR 9NE AGNE AG noticemost recent · no count stated+418d
  9. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 7, 2025 – Feb 14, 2025
ME AG
Discovered
Feb 13, 2025· 6d undetected
NE AG + HHS OCR + VT AG +1
Data types
Health (basic) · Identity (basic) · Government ID · PHI
NE AG + MA AG + VT AG +2
Attack vector
Unauthorized Access
NE 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)

237,830

Sum of filed state slices

42· 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 claim1 member

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

Press / market report

No press coverage linked yet.

State AG / regulator filing7 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 24, 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

418 days

Cadence

~1 / 59.7d

vs. multi-state median

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