DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteState AGConfirmed6 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedexfilsquadhigh sensitivity
Merged incident · 6 filings

FRONTIER AIRLINES, INC. — May 2026 breach

Clustered 6 filings across 6 jurisdictions · filing window Jul 9, 2026 → Jul 26, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

6 filings

States

5

Affected · reported

11,482

First → last filing

Jul 9, 2026 → Jul 26, 2026

Merge confidence

100%

incident inc_f8ac7dae234b437f · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion May 12, 2026–Jun 3, 2026, discovered Jun 8, 2026 — the first regulatory filing landed 31 days later. 11,482 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and Employment. Notifications rolled out on a 17-day schedule across 5 filings beginning Jul 9, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
31days

Discovered → first regulatory filing

Discovery variance
10days

Range of discovered_at dates across filings

Leak precedence
Noneclaim trailed by 17d

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

Time between earliest and latest filing

Not recorded for this incident

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

Regulatory clocksTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 12, 2026breach begins
Jun 8, 2026discovered · members disagree
notification delay · 31 days
Jul 9, 2026first filing
Jul 14, 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. JUL 9NE AGNE AG noticefirst filing · no count statedday 0
  2. JUL 9VT AGVT AG notice6 VT residentsday 0
  3. JUL 13NH AGNH AG notice11 NH residents+4d
  4. JUL 14TX AGTX AG noticestates nationwide total 11,482+5d
  5. JUL 14MA AGMA AG notice27 MA residents+5d
  6. JUL 26Leak siteexfilsquad postmost recent · attacker claim · unverified+17d
  7. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 12, 2026 – Jun 3, 2026
NE AG
Discovered
Jun 8, 2026NH AGJun 18, 2026NE AG + TX AGfilings disagree on discovery
Data types
Employment · Identity (basic) · Government ID
NE AG + NH AG + TX 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)

11,482

Sum of filed state slices

723· 6.3% of stated

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

US11,482
TX679
MA27
NH11
VT6

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 filing5 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

17 days

Cadence

~1 / 3.4d

vs. multi-state median

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