DisclosureLens
State AGConfirmed10 filings · 10 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 10 filings

CHOICE HOTELS INTERNATIONAL INC /DE — January 2026 breach

Clustered 10 filings across 10 jurisdictions · filing window Feb 19, 2026 → Feb 20, 2026 (dated filings only). View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

24,115

First → last dated filing

Feb 19, 2026 → Feb 20, 2026

Merge confidence

100%

incident inc_cfbc4377ea484341 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe a phishing attack. Intrusion Jan 14, 2026, discovered Jan 14, 2026. 24,115 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

Discovery variance
12days

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 bdayMassachusetts✓ MA credit monitoring dueOregon✓ OR AG ≤45dMaine✓ ME AG ≤30d · 24dTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 14, 2026breach begins
Jan 14, 2026discovered · members disagree
Feb 19, 2026first dated filing
Feb 20, 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 about this breach

  1. FEB 1IL AGIL AG noticefiling day not on record · no count stated—
  2. FEB 19IN AGIN AG noticefirst filing · states nationwide total 24,115day 0
  3. FEB 19NH AGNH AG notice67 NH residentsday 0
  4. FEB 19NE AGNE AG noticefiling day not on record · 198 NE residents—
  5. FEB 19CA AGCA AG noticeno count statedday 0
  6. FEB 19MA AGMA AG notice269 MA residentsday 0
  7. FEB 19OR AGOR AG noticestates nationwide total 24,115day 0
  8. FEB 19VT AGVT AG noticeno count statedday 0
  9. FEB 19ME AGME AG notice66 ME residentsday 0
  10. FEB 20TX AGTX AG noticemost recent · states nationwide total 24,115+1d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 14, 2026
IN AG
Discovered
Jan 14, 2026NE AG + CA AG + OR AG +1Jan 26, 2026IL AG + ME AG + TX AGfilings disagree on discovery
Data types
Identity (basic) · Government ID
IL AG + NH AG + NE AG +5
Attack vector
Phishing
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)

24,115

Sum of filed state slices

3,670· 15.2% of stated

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

US24,115
TX2,559
IN511
MA269
NE198
NH67
ME66

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 filing10 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.1d

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.

Choice Hotels International Inc /de data breach (2026) — filings in 10 jurisdictions, February 2026 · DisclosureLens