FRONTIER AIRLINES, INC.
bd_d3b86a2113933666 · schema v1 · pii pii-v1
Full breach record for FRONTIER AIRLINES, INC. →3 incidents on fileThreat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Exfilsquad on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
Revenue: $1.5B DATA SUMMARY: 2.4M~ records containing: significant PII, customer support cases, flight and travel information, complaint records, baggage details, and customer support email communications.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jul 26, 2026
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (5) · sorted by filing gap
- Texas State AGbd_8051a3d50d06dff82026-07-14 · +12dVerified by operator
- Massachusetts State AGbd_e689edfc5b27166b2026-07-14 · +12dVerified by operator
- New Hampshire State AGbd_eeea7b4cc582ca0c2026-07-13 · +13dVerified by operator
- Nebraska State AGbd_0974ef8675755c482026-07-09 · +17dVerified by operator
Show 1 more filing ↓Show fewer ↑up to 17d gap
- Vermont State AGbd_3790dc03c624bee32026-07-09 · +17dVerified
Filing propagation · 6 filings · 5 states
View merged incident ↗Pattern: first filing Jul 9 (NE), last Jul 26 — a 17-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.
Source ceiling
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.