Kingdom Trust — March 2024 breach
Clustered 2 filings across 2 jurisdictions · filing window Aug 23, 2024 → Aug 27, 2024. View entity profile → Other incidents for this victim →
incident inc_35b216da9cd645f1 · merged by deterministic · confidence 100%
Litigation Timing
SupplementalDiscovered → 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.
Incident timeline
Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.
Member cascade — every filing about this breach
- AUG 23CA AGCA AG noticefirst filing · no count statedauto-linkedday 0
- AUG 27NH AGNH AG noticemost recent · 24 NH residents+4d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Mar 1, 2024 CA AG
- Discovered
- Mar 1, 2024 NH AG
- Data types
- Identity (basic) · Government ID · Financial account CA AG + NH AG
- Attack vector
- Unauthorized Access CA AG
- Response
- Engaged third-party independent cybersecurity experts to conduct a thorough investigation · Notified law enforcement · Notified clients and worked with them to identify the list of potentially impacted individuals 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.
Merge provenance
- Method
- deterministic
- Confidence
- 1.00 · above the 0.85 auto-merge floor
- 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
4 days
vs. multi-state median
1.3× 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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.