Heights Finance — March 2026 breach
Clustered 3 filings across 3 jurisdictions · filing window Aug 11, 2026 → Aug 14, 2026. View entity profile → Other incidents for this victim →
incident inc_eb1877fbd2df4b1a · merged by deterministic · confidence 100%
Litigation Timing
SupplementalDiscovered → first regulatory filing
Range of discovered_at dates across filings
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.
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 11VT AGVT AG noticefirst filing · 21 VT residentsday 0
- AUG 11NH AGNH AG notice26 NH residentsauto-linkedday 0
- AUG 14TX AGTX AG noticemost recent · 734,828 affectedauto-linked+3d
- Watching for additional filings — new sources merge into this incident automatically.
Roll-up facts — reconciled across members
- Breach window
- Mar 13, 2026 – May 7, 2026 NH AG
- Discovered
- May 7, 2026· 55d undetected NH AG + TX AG
- Data types
- Government ID · Financial account · Identity (basic) VT AG + NH AG + TX AG
- Attack vector
- Third-Party / Supply Chain NH AG
- Response
- Activated its incident response protocols · Brought in outside cybersecurity specialists to investigate · Reported the incident to federal law enforcement NH AG
Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.
Affected residents by state
per-state reported counts
State AGs report only their own residents; teal bars show each state's reported slice.
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
3 days
Cadence
~1 / 1.5d
vs. multi-state median
1.7× 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.