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

Survival Flight Inc — July 2025 breach

Clustered 5 records across 4 jurisdictions: 4 filings and 1 leak-site claim · filing window Sep 15, 2025 → Mar 6, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 records

States

4

Affected · reported

97,217

First → last dated filing

Sep 15, 2025 → Mar 6, 2026

Merge confidence

100%

incident inc_9e7eb296b6a44f6c · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jul 17, 2025, discovered Jul 17, 2025 — the first regulatory filing landed 60 days later; 1 later filing was flagged late. 97,217 individuals reported across the linked filings. Data reported: Government ID, Health (basic), Financial account, and 3 more. Notifications rolled out on a 172-day schedule across 3 dated filings beginning Sep 15, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
60days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
3days 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
172days

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksMassachusetts✗ MA AG >90dLeak gap⏱ Leak >90dHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 17, 2025breach begins
Jul 17, 2025discovered
notification delay · 60 days
Sep 15, 2025first dated filing
Mar 6, 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. JUL 11Leak siteworldleaks postfirst record · attacker claim · unverifiedday 0
  2. SEP 15HHS OCRHHS OCR noticestates nationwide total 97,217+66d
  3. MAR 6MA AGMA AG notice14 MA residents+238d
  4. MAR 6MT AGMT AG noticemost recent · 10 MT residents+238d
  5. MAR 6NE AGNE AG noticefiling day not on record · no count stated—
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jul 17, 2025
MT AG
Discovered
Jul 17, 2025
MA AG + MT AG + NE AG
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + MA AG + MT AG +1
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)

97,217

Sum of filed state slices

24· 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 filing4 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 Oct 11, 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

172 days

Cadence

~1 / 86d

vs. multi-state median

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