DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
State AGConfirmed7 filings · 7 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 7 filings

Wheels Up Partners LLC — October 2025 breach

Clustered 7 filings across 7 jurisdictions · filing window Dec 9, 2025 → Dec 10, 2025 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

7 filings

States

7

Affected · reported

5,710

First → last dated filing

Dec 9, 2025 → Dec 10, 2025

Merge confidence

100%

incident inc_44f1e8865c53427a · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 7 regulatory filings. The filings describe unauthorized access. Intrusion Oct 20, 2025–Oct 20, 2025, discovered Oct 23, 2025 — the first regulatory filing landed 47 days later. 5,710 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
47days

Discovered → first regulatory filing

Discovery variance
11days

Range of discovered_at dates across filings

Filing span
1days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksVermont⏱ VT AG >14 bdayMaine⏱ ME AG >30d · 47dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 20, 2025breach begins
Oct 23, 2025discovered · members disagree
notification delay · 47 days
Dec 9, 2025first dated filing
Dec 10, 2025most 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 about this breach

  1. DEC 9IN AGIN AG noticefirst filing · states nationwide total 5,710day 0
  2. DEC 9NE AGNE AG noticefiling day not on record · 8 NE residents—
  3. DEC 9NH AGNH AG notice36 NH residentsday 0
  4. DEC 9VT AGVT AG noticeno count statedday 0
  5. DEC 9ME AGME AG noticestates nationwide total 5,710day 0
  6. DEC 10MA AGMA AG notice72 MA residents+1d
  7. DEC 10TX AGTX AG noticemost recent · states nationwide total 5,710+1d
  8. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 20, 2025
IN AG
Discovered
Oct 23, 2025NE AG + NH AG + VT AG +1Nov 3, 2025TX AGfilings disagree on discovery
Data types
Identity (basic) · Government ID
NE AG + NH AG + VT AG +3
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)

5,710

Sum of filed state slices

539· 9.4% of stated

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

US5,710
TX274
IN139
MA72
NH36
ME10
NE8

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 claim

No leak-site claim on record for this incident.

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

1 days

Cadence

~1 / 0.2d

vs. multi-state median

6.0× faster

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.