Clustered 2 filings across 2 jurisdictions · filed Nov 24, 2015. View entity profile → Other incidents for this victim →
incident inc_356e6460e4014659 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
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.
CA WA
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 18, 2014 → Jul 27, 2015
When the intrusion reportedly occurred, per the linked filings
Feb 10, 2015
Reported by WASHINGTON AG filing
Hilton Worldwide, Inc., a business sector entity reported a malware incident to the Washington Attorney General. The organization became aware of the incident on 2015-02-10 and filed notice on 2015-11-24. 287 days elapsed between awareness and notification.
Hilton Worldwide disclosed a point-of-sale malware incident affecting payment card data at its hotels. The malware ran during two windows: November 18–December 5, 2014 and April 21–July 27, 2015. Cardholder names, payment card numbers, security codes, and expiration dates were targeted. No addresses or PINs were compromised. Hilton worked with third-party forensic experts, law enforcement, and payment card companies. One year of complimentary credit monitoring through AllClear was offered to affected customers.
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.