WorldPass Travel Group, LLC — July 2010 breach
One linked filing — more sources may join as they report · filed Mar 27, 2012. View entity profile → Other incidents for this victim →
incident inc_e4790d7bb9cd42c2 · merged by deterministic
Litigation Timing
Discovered → first regulatory filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Incident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- MAR 27NH AGNH AG noticeonly filing · 1 NH residentsday 0
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Jul 1, 2010 NH AG
- Discovered
- Mar 5, 2012· 613d undetected NH AG
- Data types
- Identity (basic) · Financial account · PII NH AG
- Attack vector
- Unauthorized Access NH AG
- Response
- Shut down our entire data system to fully investigate the matter and eliminate any further unlawful access to our system · Reported this cyber-attack to the local police, the FBI, and the U.S. Secret Service · Contacted the affected customers on March 8, 2012 by email if we could, and for those we could not contact by email, by phone or regular mail NH AG
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Evidence ladder — rungs this incident occupies
No leak-site claim on record for this incident.
No press coverage linked yet.
Unlocks: discovery date, data types, affected count, compliance clock.
No SEC filing or victim statement yet.
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.