Clustered 2 filings across 2 jurisdictions · filed Aug 2, 2013. View entity profile → Other incidents for this victim →
incident inc_0af5a6c23fbc4595 · merge_method deterministic · confidence 100%
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Identity (basic) · Government ID · Financial account
CA NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
State of New Hampshire Attorney General breach notification filed by US Airways on August 2, 2013. The source document is a PDF attachment containing only page markers (pages 1-5) with no visible breach narrative, dates, or data types. Extraction is limited to the filing metadata provided in the trusted lead-in tags.
US Airways notified California regulators of a breach affecting Dividend Miles accounts. Unauthorized users obtained usernames and passwords for compromised accounts. Potentially accessed data includes names, addresses, emails, security questions, dates of birth, Known Traveler numbers, and the last four digits of credit cards. A limited number of accounts had mileage improperly taken. US Airways deactivated passwords, reset credentials, disabled security questions, and contracted with LifeLock for one year of credit monitoring services. The investigation is ongoing with federal law enforcement.
Sep 1, 2013 → Oct 27, 2013
When the intrusion reportedly occurred, per the linked filings
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.